Closed nnnnathann closed 9 years ago
@cedbossneo is/was the maintainer for the rackconnect template. corekube has been updated quite a bit since the rackconnect template was last touched.
hoping @cedbossneo can chime in and possibly update it, if not, i can examine it
FYI, I gave it another shot by just updating the commit hash for overlord in the rackconnect file, thinking maybe it was just a version mismatch issue. That failed also for a different reason
May 22 17:42:13 kubernetes-master-0 systemd[1]: master-apiserver@a4aa28b6d3a340aea9182d5795c75626.service holdoff time over, scheduling restart.
May 22 17:42:13 kubernetes-master-0 systemd[1]: Stopping Kubernetes API Server...
May 22 17:42:13 kubernetes-master-0 systemd[1]: Starting Kubernetes API Server...
May 22 17:42:13 kubernetes-master-0 systemd[1]: Failed to load environment files: No such file or directory
Probably going to stop here for now and await response, thanks so much for the help!
Also, I wouldn't mind diving in myself if you all have an idea of where to start? I'm new to a lot of things but might be able to help out with a pointer in the right direction?
Again, thanks for the time and the effort to set up this repo!
@nnnnathann your best bet is to take the corekube-rackconnect-v3.yaml (https://github.com/metral/corekube/blob/master/corekube-rackconnect-v3.yaml) and adapt it to model the corekube-cloudservers.yaml (https://github.com/metral/corekube/blob/master/corekube-cloudservers.yaml) as closely as possible. come to think of it, given that there are extra network interfaces on public cloud, the yaml file for rackconnect will probably resemble that of OnMetal (https://github.com/metral/corekube/blob/master/corekube-onmetal.yaml).
I'd start on that path and see how far it gets you. Unfortunately, I can't be of much help for RackConnect as I don't have an account to use in that environment but I can provide feedback & guidance if needed.
Please keep us posted
Hi, sorry i wasnt available last week,
I will update the template tonight/tomorrow
Regards Le 26 mai 2015 6:24 PM, "Mike Metral" notifications@github.com a écrit :
@nnnnathann https://github.com/nnnnathann your best bet is to take the corekube-rackconnect-v3.yaml ( https://github.com/metral/corekube/blob/master/corekube-rackconnect-v3.yaml) and adapt it to model the corekube-cloudservers.yaml ( https://github.com/metral/corekube/blob/master/corekube-cloudservers.yaml) as closely as possible. come to think of it, given that there are extra network interfaces on public cloud, the yaml file for rackconnect will probably resemble that of OnMetal ( https://github.com/metral/corekube/blob/master/corekube-onmetal.yaml).
I'd start on that path and see how far it gets you. Unfortunately, I can't be of much help for RackConnect as I don't have an account to use in that environment but I can provide feedback & guidance if needed.
Please keep us posted
— Reply to this email directly or view it on GitHub https://github.com/metral/corekube/issues/15#issuecomment-105588940.
I've release a updated version of the heat file but i can't test it right now, if you want to try : https://github.com/cedbossneo/corekube/tree/update-heat-file
It appears to have worked!
Thank you both.
closing due to the issue being resolved
No big deal, but I think this is not resolved technically until the aforementioned rackconnect heat file is merged?
https://github.com/cedbossneo/corekube/blob/update-heat-file/corekube-rackconnect-v3.yaml
Thanks everyone
@nnnnathann it was merged yesterday: https://github.com/metral/corekube/pull/17
is there something missing?
ha, nope, I'll see myself out. thanks again
Haha no worries. Please let us know if you encounter any other issues with Corekube
On Friday, May 29, 2015, Nathan Bleigh notifications@github.com wrote:
ha, nope, I'll see myself out. thanks again
— Reply to this email directly or view it on GitHub https://github.com/metral/corekube/issues/15#issuecomment-106834756.
-Mike Metral
Hello all,
I'm having some trouble deploying out to Rackspace (RackConnect v3) using the rackconnect-v3 yaml.
Here is the error I am getting from the overlord after deployment:
Any help would be appreciated! Thanks for this repo.