Update centos-6-openstack.ks #2
Conversation
a couple of small fixes: - enable console-logging in the way Nova expects (i.e. make `nova console-log $VM` work; see [here](https://ask.openstack.org/question/108/configuring-image-to-write-to-console-log/) for more information) - add `ec2-user` for `cloud-init` (the user that gets the SSH key injected in the default config) - add `NOZEROCONF` variable that prevents CentOS from adding a 169.254.0.0-route that troubles fetching metadata (at least with Quantum, but Zeroconf's probably not needed in a cloud VM anyways)
|
@srenatus Default policy is actually to use the 'centos' cloud user for CentOS images in openstack (see #3 ). CentOS also won't add the default metadata route if you remove NetworkManager. This actually the usual way of solving this problem. See https://github.com/dtroyer/image-recipes for some good examples |
|
hi, Firstly, apologies for not moving faster on this - 've been waiting to see how the CentOS Project conversations around the user issue go; and so far it looks like the root account is going to remain the default policy there. Having said that, we should do whatever we need to here... |
|
@kbsingh You're right that it really doesn't matter what you set the default user to. I was just pointing out that each OS has their own conventions that they use for their images. Ubuntu uses "ubuntu", RHEL uses "cloud-user" and CentOS images use 'centos'. Amazon overwrites some of these as well, so it's entirely up to you what you want to use. 😄 |
a couple of small fixes:
nova console-log $VMwork; see here for more information)ec2-userforcloud-init(the user that gets the SSH key injected in the default config)NOZEROCONFvariable that prevents CentOS from adding a 169.254.0.0-route that troubles fetching metadata (at least with Quantum, but Zeroconf's probably not needed in a cloud VM anyways)Thanks for Raindrops btw, it's quite perfect for effortless image creation... I've been waiting for this ;)