-
Notifications
You must be signed in to change notification settings - Fork 87
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Lbaasv2 #343
base: master
Are you sure you want to change the base?
Lbaasv2 #343
Conversation
This reverts commit f8a0054.
Should I make a new pull request to a new feature branch, instead of the master? |
@bartpved thx++! I implemented a different solution adding a PoolMember in every master in master.yaml. I saw you used %index%. Your solution seems cool as you didn't modify master.yaml |
cheers! :-) |
@bartpved I'm adding a lbaas configuration for the wildcard domain too (balancing nodes). Would you do it in the same lbaas.yaml or in a different one? |
Hi Gang, Still working on getting this deployed on my Openstack deployment, but somethings I noticed when deploying:
I was able to get the stack to create by adding those parameters to openstack.yaml. Not sure if this is helpful or correct. Let me know if I can provide additional information. Thanks! |
Also, I'm getting stuck on the deploy for the loadbalancer resource; any advice? Resource Create Failed: Resources.Pool Members: Resources.Loadbalancer.Property Error: Resources[0].Properties: Property Master Count Not Assigned |
@cwpenhale adding missing params is OK. About the HEAT error, looks like the param master_count is not passed properly, you will need to pass it if it's missing. |
To me it worked nicely. I just modified:
|
Hi guys,
This pull request is related to #340
We (Tieto Tecong folks) forked the repo, and did some modifications.
At this moment running OpenShift at our dev env requires quite amount of tuning (done in our fork),
so this pull request is not tested -> it contains only the lbaasv2 fucntionality.
But still it may be good enough as a starting point.
Let's see how to work on from here, in case you are interested in this feature.
We have also other smaller features and fixes, so maybe we could propose further pull requests.
In ideal case, we would want to have all out modifications upstream.
-Vedran (on behalf of the tecong team)