Hello,
Can someone more involved with the Cloud SIG advise on how to use cloud-init in such a way that it does not violate the SIG rules? I.e. please add it to one of the CentOS repos so we can use it "legally". :-) The purpose is including it in "official" Cloudstack CentOS images.
Regards, Lucian
That’d be great for the Openstack images as well! :-)
As a side note, for Openstack we need cloud-init >= 0.7.2
Alessandro
On 16 Jan 2014, at 01:10 , Nux! nux@li.nux.ro wrote:
Hello,
Can someone more involved with the Cloud SIG advise on how to use cloud-init in such a way that it does not violate the SIG rules? I.e. please add it to one of the CentOS repos so we can use it "legally". :-) The purpose is including it in "official" Cloudstack CentOS images.
Regards, Lucian
-- Sent from the Delta quadrant using Borg technology!
Nux! www.nux.ro _______________________________________________ CentOS-devel mailing list CentOS-devel@centos.org http://lists.centos.org/mailman/listinfo/centos-devel
Is EPEL not "official" enough? It has cloud-init 0.6.3.
0.7.2 is available here: http://repos.fedorapeople.org/repos/openstack/cloud-init/epel-6/
On Wed, Jan 15, 2014 at 5:19 PM, Alessandro Pilotti < apilotti@cloudbasesolutions.com> wrote:
That’d be great for the Openstack images as well! :-)
As a side note, for Openstack we need cloud-init >= 0.7.2
Alessandro
On 16 Jan 2014, at 01:10 , Nux! nux@li.nux.ro wrote:
Hello,
Can someone more involved with the Cloud SIG advise on how to use cloud-init in such a way that it does not violate the SIG rules? I.e. please add it to one of the CentOS repos so we can use it "legally". :-) The purpose is including it in "official" Cloudstack CentOS images.
Regards, Lucian
-- Sent from the Delta quadrant using Borg technology!
Nux! www.nux.ro _______________________________________________ CentOS-devel mailing list CentOS-devel@centos.org http://lists.centos.org/mailman/listinfo/centos-devel
CentOS-devel mailing list CentOS-devel@centos.org http://lists.centos.org/mailman/listinfo/centos-devel
On 16.01.2014 03:07, Logan McNaughton wrote:
Is EPEL not "official" enough? It has cloud-init 0.6.3.
It's not, too old and can't handle Cloudstack as a data source.
0.7.2 is available here: http://repos.fedorapeople.org/repos/openstack/cloud-init/epel-6/
It's what I'm using at the moment, but it needs to be internally built and hosted within CentOS somehow.
On 01/16/2014 09:54 AM, Nux! wrote:
On 16.01.2014 03:07, Logan McNaughton wrote:
Is EPEL not "official" enough? It has cloud-init 0.6.3.
It's not, too old and can't handle Cloudstack as a data source.
(I'm one of the maintainers of cloud-init in EPEL)
I will start looking into updating cloud-init in EPEL to 0.7.x. If there's a blocker for bumping the version but we can backport the cloudstack data source changeset(s) would that be an okay alternative?
0.7.2 is available here: http://repos.fedorapeople.org/repos/openstack/cloud-init/epel-6/
It's what I'm using at the moment, but it needs to be internally built and hosted within CentOS somehow.
On 01/16/2014 09:20 AM, Sam Kottler wrote:
On 01/16/2014 09:54 AM, Nux! wrote:
On 16.01.2014 03:07, Logan McNaughton wrote:
Is EPEL not "official" enough? It has cloud-init 0.6.3.
It's not, too old and can't handle Cloudstack as a data source.
(I'm one of the maintainers of cloud-init in EPEL)
I will start looking into updating cloud-init in EPEL to 0.7.x. If there's a blocker for bumping the version but we can backport the cloudstack data source changeset(s) would that be an okay alternative?
given what it is - cloud-init 7.x is the way to go really. And I think this thread really brings up the need for us to have a Cloud Instance SIG ( with a smaller sub group that handles vendor specific stuff, ideally the vendors themselves... )
Now, let me try and see if I can drag AWS down into this SIG.
- KB
On Thu, Jan 16, 2014 at 10:20:23AM +0100, Sam Kottler wrote:
I will start looking into updating cloud-init in EPEL to 0.7.x.
I'm frequently jumping between Fedora, CentOS, and RHEL, and I would love to see version parity for cloud-init across the board. There were substantial changes between 0.6.x and 0.7.x so backporting support might be tricky in any case.
For OpenStack we need 0.7.x. It'll be great if we could have it in EPEL.
On 16.01.2014, at 16:30, "Lars Kellogg-Stedman" lars@redhat.com wrote:
On Thu, Jan 16, 2014 at 10:20:23AM +0100, Sam Kottler wrote: I will start looking into updating cloud-init in EPEL to 0.7.x.
I'm frequently jumping between Fedora, CentOS, and RHEL, and I would love to see version parity for cloud-init across the board. There were substantial changes between 0.6.x and 0.7.x so backporting support might be tricky in any case.
-- Lars Kellogg-Stedman lars@redhat.com | larsks @ irc Cloud Engineering / OpenStack | " " @ twitter
CentOS-devel mailing list CentOS-devel@centos.org http://lists.centos.org/mailman/listinfo/centos-devel
On 01/16/2014 04:11 PM, Alessandro Pilotti wrote:
For OpenStack we need 0.7.x. It'll be great if we could have it in EPEL.
reporting from a conversation on irc earlier today, Sam is going to push getting cloud-init 0.7.x into EPEL-6 within a few days time.
that then means we dont need to own cloud-init in CentOS-Extras/ for now, and images we ship will retain an upgrade path for the code/content inside that.
I think its worth waiting for the newer cloud-init to arrive in epel.
- KB
On 01/22/2014 12:19 AM, Karanbir Singh wrote:
On 01/16/2014 04:11 PM, Alessandro Pilotti wrote:
For OpenStack we need 0.7.x. It'll be great if we could have it in EPEL.
reporting from a conversation on irc earlier today, Sam is going to push getting cloud-init 0.7.x into EPEL-6 within a few days time.
that then means we dont need to own cloud-init in CentOS-Extras/ for now, and images we ship will retain an upgrade path for the code/content inside that.
I think its worth waiting for the newer cloud-init to arrive in epel.
there is a possibility that we can get 0.7.5 of cloud-init, which will help resolve a bunch of issues with opennebula and cloudstack issues as well.
On 01/22/2014 05:01 PM, Karanbir Singh wrote:
On 01/22/2014 12:19 AM, Karanbir Singh wrote:
On 01/16/2014 04:11 PM, Alessandro Pilotti wrote:
For OpenStack we need 0.7.x. It'll be great if we could have it in EPEL.
reporting from a conversation on irc earlier today, Sam is going to push getting cloud-init 0.7.x into EPEL-6 within a few days time.
that then means we dont need to own cloud-init in CentOS-Extras/ for now, and images we ship will retain an upgrade path for the code/content inside that.
I think its worth waiting for the newer cloud-init to arrive in epel.
there is a possibility that we can get 0.7.5 of cloud-init, which will help resolve a bunch of issues with opennebula and cloudstack issues as well.
0.7.5 is not released upstream yet AFAICT despite their documentation site and other stuff being updated. Can anyone confirm this? The version that's in ubuntu seems to be built straight from bzr. I've just committed a pretty large changeset that bumps to 0.7.4; thanks to Lars Kellogg-Stedman and Steve Hardy for their assistance. There are still some dependency issues which I'm working on fixing now, but those should hopefully be taken care of soon.
On Wed, Jan 22, 2014 at 6:12 PM, Sam Kottler s@shk.io wrote:
On 01/22/2014 05:01 PM, Karanbir Singh wrote:
On 01/22/2014 12:19 AM, Karanbir Singh wrote:
On 01/16/2014 04:11 PM, Alessandro Pilotti wrote:
For OpenStack we need 0.7.x. It'll be great if we could have it in
EPEL.
reporting from a conversation on irc earlier today, Sam is going to
push
getting cloud-init 0.7.x into EPEL-6 within a few days time.
that then means we dont need to own cloud-init in CentOS-Extras/ for now, and images we ship will retain an upgrade path for the
code/content
inside that.
I think its worth waiting for the newer cloud-init to arrive in epel.
there is a possibility that we can get 0.7.5 of cloud-init, which will help resolve a bunch of issues with opennebula and cloudstack issues as well.
0.7.5 is not released upstream yet AFAICT despite their documentation site and other stuff being updated. Can anyone confirm this?
Confirmed. 0.7.5 isn't out yet. 0.7.4 isn't good enough?
...Juerg
The version that's in ubuntu seems to be built straight from bzr. I've just committed a pretty large changeset that bumps to 0.7.4; thanks to Lars Kellogg-Stedman and Steve Hardy for their assistance. There are still some dependency issues which I'm working on fixing now, but those should hopefully be taken care of soon.
CentOS-devel mailing list CentOS-devel@centos.org http://lists.centos.org/mailman/listinfo/centos-devel
On Jan 22, 2014, at 6:27 PM, Juerg Haefliger juergh@gmail.com wrote:
On Wed, Jan 22, 2014 at 6:12 PM, Sam Kottler s@shk.io wrote:
On 01/22/2014 05:01 PM, Karanbir Singh wrote:
On 01/22/2014 12:19 AM, Karanbir Singh wrote:
On 01/16/2014 04:11 PM, Alessandro Pilotti wrote:
For OpenStack we need 0.7.x. It'll be great if we could have it in EPEL.
reporting from a conversation on irc earlier today, Sam is going to push getting cloud-init 0.7.x into EPEL-6 within a few days time.
that then means we dont need to own cloud-init in CentOS-Extras/ for now, and images we ship will retain an upgrade path for the code/content inside that.
I think its worth waiting for the newer cloud-init to arrive in epel.
there is a possibility that we can get 0.7.5 of cloud-init, which will help resolve a bunch of issues with opennebula and cloudstack issues as well.
0.7.5 is not released upstream yet AFAICT despite their documentation site and other stuff being updated. Can anyone confirm this?
Confirmed. 0.7.5 isn't out yet. 0.7.4 isn't good enough?
0.7.2 should be enough for CloudStack
-sebastien
...Juerg
The version that's in ubuntu seems to be built straight from bzr. I've just committed a pretty large changeset that bumps to 0.7.4; thanks to Lars Kellogg-Stedman and Steve Hardy for their assistance. There are still some dependency issues which I'm working on fixing now, but those should hopefully be taken care of soon.
CentOS-devel mailing list CentOS-devel@centos.org http://lists.centos.org/mailman/listinfo/centos-devel
CentOS-devel mailing list CentOS-devel@centos.org http://lists.centos.org/mailman/listinfo/centos-devel
For OpenNebula we need at least version 0.7.3.
On Wed, Jan 22, 2014 at 6:49 PM, sebgoa runseb@gmail.com wrote:
On Jan 22, 2014, at 6:27 PM, Juerg Haefliger juergh@gmail.com wrote:
On Wed, Jan 22, 2014 at 6:12 PM, Sam Kottler s@shk.io wrote:
On 01/22/2014 05:01 PM, Karanbir Singh wrote:
On 01/22/2014 12:19 AM, Karanbir Singh wrote:
On 01/16/2014 04:11 PM, Alessandro Pilotti wrote:
For OpenStack we need 0.7.x. It'll be great if we could have it in EPEL.
reporting from a conversation on irc earlier today, Sam is going to push getting cloud-init 0.7.x into EPEL-6 within a few days time.
that then means we dont need to own cloud-init in CentOS-Extras/ for now, and images we ship will retain an upgrade path for the code/content inside that.
I think its worth waiting for the newer cloud-init to arrive in epel.
there is a possibility that we can get 0.7.5 of cloud-init, which will help resolve a bunch of issues with opennebula and cloudstack issues as well.
0.7.5 is not released upstream yet AFAICT despite their documentation site and other stuff being updated. Can anyone confirm this?
Confirmed. 0.7.5 isn't out yet. 0.7.4 isn't good enough?
0.7.2 should be enough for CloudStack
-sebastien
...Juerg
The version that's in ubuntu seems to be built straight from bzr. I've just committed a pretty large changeset that bumps to 0.7.4; thanks to Lars Kellogg-Stedman and Steve Hardy for their assistance. There are still some dependency issues which I'm working on fixing now, but those should hopefully be taken care of soon.
CentOS-devel mailing list CentOS-devel@centos.org http://lists.centos.org/mailman/listinfo/centos-devel
CentOS-devel mailing list CentOS-devel@centos.org http://lists.centos.org/mailman/listinfo/centos-devel
CentOS-devel mailing list CentOS-devel@centos.org http://lists.centos.org/mailman/listinfo/centos-devel
On 01/23/2014 10:34 AM, Javier Fontan wrote:
For OpenNebula we need at least version 0.7.3.
Great, thanks. So 0.7.4 seems like it'll be okay for all the people who requested more recent versions. There are two dependencies which are pending push to EPEL updates; once those are available (tonight's push) I will add them as requires to the cloud-init spec and submit an update.
Thanks for your patience on this.
-S
On Wed, Jan 22, 2014 at 6:49 PM, sebgoa runseb@gmail.com wrote:
On Jan 22, 2014, at 6:27 PM, Juerg Haefliger juergh@gmail.com wrote:
On Wed, Jan 22, 2014 at 6:12 PM, Sam Kottler s@shk.io wrote:
On 01/22/2014 05:01 PM, Karanbir Singh wrote:
On 01/22/2014 12:19 AM, Karanbir Singh wrote:
On 01/16/2014 04:11 PM, Alessandro Pilotti wrote: > For OpenStack we need 0.7.x. It'll be great if we could have it in EPEL. >
reporting from a conversation on irc earlier today, Sam is going to push getting cloud-init 0.7.x into EPEL-6 within a few days time.
that then means we dont need to own cloud-init in CentOS-Extras/ for now, and images we ship will retain an upgrade path for the code/content inside that.
I think its worth waiting for the newer cloud-init to arrive in epel.
there is a possibility that we can get 0.7.5 of cloud-init, which will help resolve a bunch of issues with opennebula and cloudstack issues as well.
0.7.5 is not released upstream yet AFAICT despite their documentation site and other stuff being updated. Can anyone confirm this?
Confirmed. 0.7.5 isn't out yet. 0.7.4 isn't good enough?
0.7.2 should be enough for CloudStack
-sebastien
...Juerg
The version that's in ubuntu seems to be built straight from bzr. I've just committed a pretty large changeset that bumps to 0.7.4; thanks to Lars Kellogg-Stedman and Steve Hardy for their assistance. There are still some dependency issues which I'm working on fixing now, but those should hopefully be taken care of soon.
CentOS-devel mailing list CentOS-devel@centos.org http://lists.centos.org/mailman/listinfo/centos-devel
CentOS-devel mailing list CentOS-devel@centos.org http://lists.centos.org/mailman/listinfo/centos-devel
CentOS-devel mailing list CentOS-devel@centos.org http://lists.centos.org/mailman/listinfo/centos-devel
On 01/23/2014 10:49 AM, Sam Kottler wrote:
On 01/23/2014 10:34 AM, Javier Fontan wrote:
For OpenNebula we need at least version 0.7.3.
Great, thanks. So 0.7.4 seems like it'll be okay for all the people who requested more recent versions. There are two dependencies which are pending push to EPEL updates; once those are available (tonight's push) I will add them as requires to the cloud-init spec and submit an update.
I've submitted the update: https://admin.fedoraproject.org/updates/cloud-init-0.7.4-1.el6. Auto-karma is disabled because I'd like the opennebula and cloudstack folks specifically to test it, but if you're on EC2/OpenStack or any of the other supported platforms it'd be great to have this tested as well.
Thanks and have a great weekend!
-S
Thanks for your patience on this.
-S
On Wed, Jan 22, 2014 at 6:49 PM, sebgoa runseb@gmail.com wrote:
On Jan 22, 2014, at 6:27 PM, Juerg Haefliger juergh@gmail.com wrote:
On Wed, Jan 22, 2014 at 6:12 PM, Sam Kottler s@shk.io wrote:
On 01/22/2014 05:01 PM, Karanbir Singh wrote:
On 01/22/2014 12:19 AM, Karanbir Singh wrote: > On 01/16/2014 04:11 PM, Alessandro Pilotti wrote: >> For OpenStack we need 0.7.x. It'll be great if we could have it in EPEL. >> > > reporting from a conversation on irc earlier today, Sam is going to push > getting cloud-init 0.7.x into EPEL-6 within a few days time. > > that then means we dont need to own cloud-init in CentOS-Extras/ for > now, and images we ship will retain an upgrade path for the code/content > inside that. > > I think its worth waiting for the newer cloud-init to arrive in epel.
there is a possibility that we can get 0.7.5 of cloud-init, which will help resolve a bunch of issues with opennebula and cloudstack issues as well.
0.7.5 is not released upstream yet AFAICT despite their documentation site and other stuff being updated. Can anyone confirm this?
Confirmed. 0.7.5 isn't out yet. 0.7.4 isn't good enough?
0.7.2 should be enough for CloudStack
-sebastien
...Juerg
The version that's in ubuntu seems to be built straight from bzr. I've just committed a pretty large changeset that bumps to 0.7.4; thanks to Lars Kellogg-Stedman and Steve Hardy for their assistance. There are still some dependency issues which I'm working on fixing now, but those should hopefully be taken care of soon.
CentOS-devel mailing list CentOS-devel@centos.org http://lists.centos.org/mailman/listinfo/centos-devel
CentOS-devel mailing list CentOS-devel@centos.org http://lists.centos.org/mailman/listinfo/centos-devel
CentOS-devel mailing list CentOS-devel@centos.org http://lists.centos.org/mailman/listinfo/centos-devel
On 25.01.2014 13:58, Sam Kottler wrote:
I've submitted the update: https://admin.fedoraproject.org/updates/cloud-init-0.7.4-1.el6. Auto-karma is disabled because I'd like the opennebula and cloudstack folks specifically to test it, but if you're on EC2/OpenStack or any of the other supported platforms it'd be great to have this tested as well.
Thanks and have a great weekend!
Thank you, Sam. Sadly 0.7.4 is not able to use Cloudstack properly, at least the root password feature does not work, nor does the resizefs one although it's listed in cloud_init_modules. I've also built 0.7.5 and it has the same problems. More testing is needed to clarify why this happens.
Regards, Lucian
On 01/25/2014 04:58 PM, Nux! wrote:
Sadly 0.7.4 is not able to use Cloudstack properly, at least the root password feature does not work, nor does the resizefs one although it's listed in cloud_init_modules. I've also built 0.7.5 and it has the same problems. More testing is needed to clarify why this happens.
given that cloud-init does work and do the right thing for eucalyptus and openstack ( I've just tested those two ) - what fails for CloudInit ? is the data provider from CS itself incomplete or not hooking into the right place ?
On 26.01.2014 20:59, Karanbir Singh wrote:
given that cloud-init does work and do the right thing for eucalyptus and openstack ( I've just tested those two ) - what fails for CloudInit ? is the data provider from CS itself incomplete or not hooking into the right place ?
I have not tested ssh key and/or user data functionality, I believe this was already reported to work[1], but from my tests cloud-init never makes a request to the virtual router on port 8080 to retrieve the password. Why that is, I'll leave it to someone who knows how cloud-init works and can read code...
[1] http://shankerbalan.net/blog/ssh-keys-on-cloudstack-guest-instances-using-cl...
On 26.01.2014 22:47, Nux! wrote:
On 26.01.2014 20:59, Karanbir Singh wrote:
given that cloud-init does work and do the right thing for eucalyptus and openstack ( I've just tested those two ) - what fails for CloudInit ? is the data provider from CS itself incomplete or not hooking into the right place ?
I have not tested ssh key and/or user data functionality, I believe this was already reported to work[1], but from my tests cloud-init never makes a request to the virtual router on port 8080 to retrieve the password. Why that is, I'll leave it to someone who knows how cloud-init works and can read code...
[1] http://shankerbalan.net/blog/ssh-keys-on-cloudstack-guest-instances-using-cl...
Furthermore, cloud-init does seem to be trying various stuff as it can be seen from the virtual router's apache logs, but it makes 0 requests (verified via tcpdump) to the password service on port 8080:
"GET //latest/meta-data/instance-id HTTP/1.1" 200 241 "-" "Cloud-Init/0.7.4" "GET //latest/user-data HTTP/1.1" 200 222 "-" "Python-urllib/2.6" "GET //latest/meta-data/ HTTP/1.1" 200 361 "-" "Python-urllib/2.6" "GET //latest/meta-data/ HTTP/1.1" 200 361 "-" "Python-urllib/2.6" "GET //latest/meta-data/local-ipv4 HTTP/1.1" 200 236 "-" "Python-urllib/2.6" "GET //latest/meta-data/local-hostname HTTP/1.1" 200 224 "-" "Python-urllib/2.6" "GET //latest/meta-data/public-hostname HTTP/1.1" 200 222 "-" "Python-urllib/2.6" "GET //latest/meta-data/public-keys HTTP/1.1" 200 222 "-" "Python-urllib/2.6" "GET //latest/meta-data/cloud-identifier HTTP/1.1" 200 273 "-" "Python-urllib/2.6" "GET //latest/meta-data/service-offering HTTP/1.1" 200 242 "-" "Python-urllib/2.6" "GET //latest/meta-data/public-ipv4 HTTP/1.1" 200 236 "-" "Python-urllib/2.6" "GET //latest/meta-data/vm-id HTTP/1.1" 200 260 "-" "Python-urllib/2.6" "GET //latest/meta-data/availability-zone HTTP/1.1" 200 233 "-" "Python-urllib/2.6" "GET //latest/meta-data/instance-id HTTP/1.1" 200 260 "-" "Python-urllib/2.6"
The weird thing is that it does indeed change the password, because the default password no longer works, but to what, I do not know.
[root@ce ~]# grep -i password /var/log/cloud-init.log Jan 26 23:46:52 ce [CLOUDINIT] importer.py[DEBUG]: Looking for modules ['cc_set_passwords', 'cloudinit.config.cc_set_passwords'] that have attributes ['handle'] Jan 26 23:46:52 ce [CLOUDINIT] importer.py[DEBUG]: Found cc_set_passwords with attributes ['handle'] in ['cloudinit.config.cc_set_passwords'] Jan 26 23:46:52 ce [CLOUDINIT] util.py[DEBUG]: Writing to /var/lib/cloud/instances/e4212973-1224-43f9-aba9-d1582bf8d881/sem/config_set_passwords - wb: [420] 20 bytes Jan 26 23:46:52 ce [CLOUDINIT] util.py[DEBUG]: Restoring selinux mode for /var/lib/cloud/instances/e4212973-1224-43f9-aba9-d1582bf8d881/sem/config_set_passwords (recursive=False) Jan 26 23:46:52 ce [CLOUDINIT] util.py[DEBUG]: Restoring selinux mode for /var/lib/cloud/instances/e4212973-1224-43f9-aba9-d1582bf8d881/sem/config_set_passwords (recursive=False) Jan 26 23:46:52 ce [CLOUDINIT] helpers.py[DEBUG]: Running config-set-passwords using lock (<FileLock using file '/var/lib/cloud/instances/e4212973-1224-43f9-aba9-d1582bf8d881/sem/config_set_passwords'>) Jan 26 23:46:52 ce [CLOUDINIT] cc_set_passwords.py[DEBUG]: Replacing auth line 66 with yes Jan 26 23:46:52 ce [CLOUDINIT] cc_set_passwords.py[DEBUG]: Restarted the ssh daemon Jan 26 23:51:44 ce [CLOUDINIT] importer.py[DEBUG]: Looking for modules ['cc_set_passwords', 'cloudinit.config.cc_set_passwords'] that have attributes ['handle'] Jan 26 23:51:44 ce [CLOUDINIT] importer.py[DEBUG]: Found cc_set_passwords with attributes ['handle'] in ['cloudinit.config.cc_set_passwords'] Jan 26 23:51:44 ce [CLOUDINIT] helpers.py[DEBUG]: config-set-passwords already ran (freq=once-per-instance) [root@ce ~]# cat /var/lib/cloud/instances/e4212973-1224-43f9-aba9-d1582bf8d881/sem/config_set_passwords 1261: 1390780012.61
So, I would say Cloudstack support is incomplete at this time, unless someone tells me I need to enable some other module. I'll look up in the following days how to hook a script into it, perhaps we can do it this way.
On Jan 26, 2014, at 7:09 PM, Nux! nux@li.nux.ro wrote:
On 26.01.2014 22:47, Nux! wrote:
On 26.01.2014 20:59, Karanbir Singh wrote:
given that cloud-init does work and do the right thing for eucalyptus and openstack ( I've just tested those two ) - what fails for CloudInit ? is the data provider from CS itself incomplete or not hooking into the right place ?
I have not tested ssh key and/or user data functionality, I believe this was already reported to work[1], but from my tests cloud-init never makes a request to the virtual router on port 8080 to retrieve the password. Why that is, I'll leave it to someone who knows how cloud-init works and can read code... [1] http://shankerbalan.net/blog/ssh-keys-on-cloudstack-guest-instances-using-cl...
Furthermore, cloud-init does seem to be trying various stuff as it can be seen from the virtual router's apache logs, but it makes 0 requests (verified via tcpdump) to the password service on port 8080:
"GET //latest/meta-data/instance-id HTTP/1.1" 200 241 "-" "Cloud-Init/0.7.4" "GET //latest/user-data HTTP/1.1" 200 222 "-" "Python-urllib/2.6" "GET //latest/meta-data/ HTTP/1.1" 200 361 "-" "Python-urllib/2.6" "GET //latest/meta-data/ HTTP/1.1" 200 361 "-" "Python-urllib/2.6" "GET //latest/meta-data/local-ipv4 HTTP/1.1" 200 236 "-" "Python-urllib/2.6" "GET //latest/meta-data/local-hostname HTTP/1.1" 200 224 "-" "Python-urllib/2.6" "GET //latest/meta-data/public-hostname HTTP/1.1" 200 222 "-" "Python-urllib/2.6" "GET //latest/meta-data/public-keys HTTP/1.1" 200 222 "-" "Python-urllib/2.6" "GET //latest/meta-data/cloud-identifier HTTP/1.1" 200 273 "-" "Python-urllib/2.6" "GET //latest/meta-data/service-offering HTTP/1.1" 200 242 "-" "Python-urllib/2.6" "GET //latest/meta-data/public-ipv4 HTTP/1.1" 200 236 "-" "Python-urllib/2.6" "GET //latest/meta-data/vm-id HTTP/1.1" 200 260 "-" "Python-urllib/2.6" "GET //latest/meta-data/availability-zone HTTP/1.1" 200 233 "-" "Python-urllib/2.6" "GET //latest/meta-data/instance-id HTTP/1.1" 200 260 "-" "Python-urllib/2.6"
The weird thing is that it does indeed change the password, because the default password no longer works, but to what, I do not know.
[root@ce ~]# grep -i password /var/log/cloud-init.log Jan 26 23:46:52 ce [CLOUDINIT] importer.py[DEBUG]: Looking for modules ['cc_set_passwords', 'cloudinit.config.cc_set_passwords'] that have attributes ['handle'] Jan 26 23:46:52 ce [CLOUDINIT] importer.py[DEBUG]: Found cc_set_passwords with attributes ['handle'] in ['cloudinit.config.cc_set_passwords'] Jan 26 23:46:52 ce [CLOUDINIT] util.py[DEBUG]: Writing to /var/lib/cloud/instances/e4212973-1224-43f9-aba9-d1582bf8d881/sem/config_set_passwords - wb: [420] 20 bytes Jan 26 23:46:52 ce [CLOUDINIT] util.py[DEBUG]: Restoring selinux mode for /var/lib/cloud/instances/e4212973-1224-43f9-aba9-d1582bf8d881/sem/config_set_passwords (recursive=False) Jan 26 23:46:52 ce [CLOUDINIT] util.py[DEBUG]: Restoring selinux mode for /var/lib/cloud/instances/e4212973-1224-43f9-aba9-d1582bf8d881/sem/config_set_passwords (recursive=False) Jan 26 23:46:52 ce [CLOUDINIT] helpers.py[DEBUG]: Running config-set-passwords using lock (<FileLock using file '/var/lib/cloud/instances/e4212973-1224-43f9-aba9-d1582bf8d881/sem/config_set_passwords'>) Jan 26 23:46:52 ce [CLOUDINIT] cc_set_passwords.py[DEBUG]: Replacing auth line 66 with yes Jan 26 23:46:52 ce [CLOUDINIT] cc_set_passwords.py[DEBUG]: Restarted the ssh daemon Jan 26 23:51:44 ce [CLOUDINIT] importer.py[DEBUG]: Looking for modules ['cc_set_passwords', 'cloudinit.config.cc_set_passwords'] that have attributes ['handle'] Jan 26 23:51:44 ce [CLOUDINIT] importer.py[DEBUG]: Found cc_set_passwords with attributes ['handle'] in ['cloudinit.config.cc_set_passwords'] Jan 26 23:51:44 ce [CLOUDINIT] helpers.py[DEBUG]: config-set-passwords already ran (freq=once-per-instance) [root@ce ~]# cat /var/lib/cloud/instances/e4212973-1224-43f9-aba9-d1582bf8d881/sem/config_set_passwords 1261: 1390780012.61
So, I would say Cloudstack support is incomplete at this time, unless someone tells me I need to enable some other module. I'll look up in the following days how to hook a script into it, perhaps we can do it this way.
Nux, I think this might be due to this bug reported on ubuntu lists: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1250398
the cause might be an upgrade of boto. Let's discuss and test off list to see how we can solve this.
-sebastien
-- Sent from the Delta quadrant using Borg technology!
Nux! www.nux.ro
On 27.01.2014 08:42, Sebastien Goasguen wrote:
So, I would say Cloudstack support is incomplete at this time, unless someone tells me I need to enable some other module. I'll look up in the following days how to hook a script into it, perhaps we can do it this way.
Nux, I think this might be due to this bug reported on ubuntu lists: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1250398
the cause might be an upgrade of boto. Let's discuss and test off list to see how we can solve this.
-sebastien
Sebastien,
I'm already patching for that problem in the ks so it's not it: http://li.nux.ro/download/cloudstack/ks/CentOS6_x86_64_CloudStack-6.5-201401... (search for boto)
The problem is that the "set-password" function in cloud-init seems to be totally unrelated to Cloudstack's password feature. I'm trying to find a solution.
On 01/27/2014 10:55 AM, Nux! wrote:
On 27.01.2014 08:42, Sebastien Goasguen wrote:
So, I would say Cloudstack support is incomplete at this time, unless someone tells me I need to enable some other module. I'll look up in the following days how to hook a script into it, perhaps we can do it this way.
Nux, I think this might be due to this bug reported on ubuntu lists: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1250398
the cause might be an upgrade of boto. Let's discuss and test off list to see how we can solve this.
-sebastien
Sebastien,
I'm already patching for that problem in the ks so it's not it: http://li.nux.ro/download/cloudstack/ks/CentOS6_x86_64_CloudStack-6.5-201401... (search for boto)
The problem is that the "set-password" function in cloud-init seems to be totally unrelated to Cloudstack's password feature. I'm trying to find a solution.
I don't have access to a CloudStack deployment so this is difficult for me to debug. Did you manage to get resize2fs working on boot?
On 27.01.2014 10:06, Sam Kottler wrote:
On 01/27/2014 10:55 AM, Nux! wrote:
On 27.01.2014 08:42, Sebastien Goasguen wrote:
So, I would say Cloudstack support is incomplete at this time, unless someone tells me I need to enable some other module. I'll look up in the following days how to hook a script into it, perhaps we can do it this way.
Nux, I think this might be due to this bug reported on ubuntu lists: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1250398
the cause might be an upgrade of boto. Let's discuss and test off list to see how we can solve this.
-sebastien
Sebastien,
I'm already patching for that problem in the ks so it's not it: http://li.nux.ro/download/cloudstack/ks/CentOS6_x86_64_CloudStack-6.5-201401... (search for boto)
The problem is that the "set-password" function in cloud-init seems to be totally unrelated to Cloudstack's password feature. I'm trying to find a solution.
I don't have access to a CloudStack deployment so this is difficult for me to debug. Did you manage to get resize2fs working on boot?
Thanks Sam and Alan, I'm sure I'll get the resize feature working as well, I'm also using the growroot dracut module, so need to make sure they play fair. It's not boto's fault as far as I can tell, but I'll investigate more.
Sebastien, I managed to get the password feature working by dropping cloud-set-password in /var/lib/cloud/scripts/per-boot/ , personally I am happy with that until ACS is better supported upstream. You need to run dos2unix on the script as it seems to have been edited on Windows. If you are happy with this, too I can ammend the kickstarts.
Lucian
2014-01-27 Sebastien Goasguen runseb@gmail.com:
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1250398 the cause might be an upgrade of boto.
To test this theory, please try https://admin.fedoraproject.org/updates/FEDORA-EPEL-2014-0333/cloud-init-0.7... together with https://admin.fedoraproject.org/updates/FEDORA-EPEL-2014-0268/python-boto-2....
Cheers, Alan
On Sat, Jan 25, 2014 at 5:58 PM, Nux! nux@li.nux.ro wrote:
On 25.01.2014 13:58, Sam Kottler wrote:
I've submitted the update: https://admin.fedoraproject.org/updates/cloud-init-0.7.4-1.el6. Auto-karma is disabled because I'd like the opennebula and cloudstack folks specifically to test it, but if you're on EC2/OpenStack or any of the other supported platforms it'd be great to have this tested as well.
Thanks and have a great weekend!
Thank you, Sam. Sadly 0.7.4 is not able to use Cloudstack properly, at least the root password feature does not work, nor does the resizefs one although it's listed in cloud_init_modules.
The CentOS 6 kernel can't do online partition resizing so you need to install the cloud-initramfs-growroot and cloud-utils-growroot packages to do the partition resizing in the initrd. I'm the package maintainer of those two in EPEL6, let me know if you run into any issues. After the partition is resized, cloud-init will grow the filesystem to the max possible size. Newer kernels don't require the initrd-hack and cloud-init can to both partition and filesystem resizing post-initrd.
...Juerg
I've also built 0.7.5 and it has the same problems. More testing is needed to clarify why this happens.
Regards, Lucian
-- Sent from the Delta quadrant using Borg technology!
Nux! www.nux.ro _______________________________________________ CentOS-devel mailing list CentOS-devel@centos.org http://lists.centos.org/mailman/listinfo/centos-devel
On 27.01.2014 15:13, Juerg Haefliger wrote:
The CentOS 6 kernel can't do online partition resizing so you need to install the cloud-initramfs-growroot and cloud-utils-growroot packages to do the partition resizing in the initrd. I'm the package maintainer of those two in EPEL6, let me know if you run into any issues. After the partition is resized, cloud-init will grow the filesystem to the max possible size. Newer kernels don't require the initrd-hack and cloud-init can to both partition and filesystem resizing post-initrd.
...Juerg
Hello Juerg,
I have tested the resize feature and it does not work. The dracut module does it job and resizes the partition, but the filesystem is not expanded. `resize2fs /dev/vda1` worked a treat, I could add it in /var/lib/cloud/scripts/per-once/, but sounds a bit redundant since cloud-init should do this. I do have resizefs in cloud_init_modules.
Hi Sam,
On Sat, Jan 25, 2014 at 2:58 PM, Sam Kottler s@shk.io wrote:
On 01/23/2014 10:49 AM, Sam Kottler wrote:
On 01/23/2014 10:34 AM, Javier Fontan wrote:
For OpenNebula we need at least version 0.7.3.
Great, thanks. So 0.7.4 seems like it'll be okay for all the people who requested more recent versions. There are two dependencies which are pending push to EPEL updates; once those are available (tonight's push) I will add them as requires to the cloud-init spec and submit an update.
I've submitted the update: https://admin.fedoraproject.org/updates/cloud-init-0.7.4-1.el6. Auto-karma is disabled because I'd like the opennebula and cloudstack folks specifically to test it, but if you're on EC2/OpenStack or any of the other supported platforms it'd be great to have this tested as well.
Tested on OpenStack. Missing dependencies: - python-jsonpatch - python-oauth
and cloudinit/source/DataSourceSmartOS.py imports 'serial' (provided by package pyserial) which is not available in EPEL6/CentOS6. We should probably disable this datasource for EPEL6.
The rest looks fine although I didn't do extensive testing.
...Juerg
Thanks and have a great weekend!
-S
Thanks for your patience on this.
-S
On Wed, Jan 22, 2014 at 6:49 PM, sebgoa runseb@gmail.com wrote:
On Jan 22, 2014, at 6:27 PM, Juerg Haefliger juergh@gmail.com wrote:
On Wed, Jan 22, 2014 at 6:12 PM, Sam Kottler s@shk.io wrote:
On 01/22/2014 05:01 PM, Karanbir Singh wrote: > On 01/22/2014 12:19 AM, Karanbir Singh wrote: >> On 01/16/2014 04:11 PM, Alessandro Pilotti wrote: >>> For OpenStack we need 0.7.x. It'll be great if we could have it
in EPEL.
>>> >> >> reporting from a conversation on irc earlier today, Sam is going
to push
>> getting cloud-init 0.7.x into EPEL-6 within a few days time. >> >> that then means we dont need to own cloud-init in CentOS-Extras/
for
>> now, and images we ship will retain an upgrade path for the
code/content
>> inside that. >> >> I think its worth waiting for the newer cloud-init to arrive in
epel.
> > there is a possibility that we can get 0.7.5 of cloud-init, which
will
> help resolve a bunch of issues with opennebula and cloudstack
issues as
> well.
0.7.5 is not released upstream yet AFAICT despite their
documentation
site and other stuff being updated. Can anyone confirm this?
Confirmed. 0.7.5 isn't out yet. 0.7.4 isn't good enough?
0.7.2 should be enough for CloudStack
-sebastien
...Juerg
The version that's in ubuntu seems to be built straight from bzr. I've just committed a pretty large changeset that bumps to 0.7.4; thanks to
Lars
Kellogg-Stedman and Steve Hardy for their assistance. There are
still
some dependency issues which I'm working on fixing now, but those
should
hopefully be taken care of soon.
> > _______________________________________________ CentOS-devel mailing list CentOS-devel@centos.org http://lists.centos.org/mailman/listinfo/centos-devel
CentOS-devel mailing list CentOS-devel@centos.org http://lists.centos.org/mailman/listinfo/centos-devel
CentOS-devel mailing list CentOS-devel@centos.org http://lists.centos.org/mailman/listinfo/centos-devel
CentOS-devel mailing list CentOS-devel@centos.org http://lists.centos.org/mailman/listinfo/centos-devel
On 01/27/2014 04:07 PM, Juerg Haefliger wrote:
Hi Sam,
On Sat, Jan 25, 2014 at 2:58 PM, Sam Kottler <s@shk.io mailto:s@shk.io> wrote:
On 01/23/2014 10:49 AM, Sam Kottler wrote:
On 01/23/2014 10:34 AM, Javier Fontan wrote:
For OpenNebula we need at least version 0.7.3.
Great, thanks. So 0.7.4 seems like it'll be okay for all the people who requested more recent versions. There are two dependencies which are pending push to EPEL updates; once those are available (tonight's push) I will add them as requires to the cloud-init spec and submit an update.
I've submitted the update: https://admin.fedoraproject.org/updates/cloud-init-0.7.4-1.el6. Auto-karma is disabled because I'd like the opennebula and cloudstack folks specifically to test it, but if you're on EC2/OpenStack or any of the other supported platforms it'd be great to have this tested as well.
Tested on OpenStack. Missing dependencies:
- python-jsonpatch
- python-oauth
Both of these should be available in EPEL as of late last week. Do you have the repos mirrored locally and haven't updated in a while?
-S
and cloudinit/source/DataSourceSmartOS.py imports 'serial' (provided by package pyserial) which is not available in EPEL6/CentOS6. We should probably disable this datasource for EPEL6.
The rest looks fine although I didn't do extensive testing.
...Juerg
Thanks and have a great weekend!
-S
Thanks for your patience on this.
-S
On Wed, Jan 22, 2014 at 6:49 PM, sebgoa <runseb@gmail.com
mailto:runseb@gmail.com> wrote:
On Jan 22, 2014, at 6:27 PM, Juerg Haefliger <juergh@gmail.com
mailto:juergh@gmail.com> wrote:
On Wed, Jan 22, 2014 at 6:12 PM, Sam Kottler <s@shk.io
mailto:s@shk.io> wrote:
> > > > On 01/22/2014 05:01 PM, Karanbir Singh wrote: >> On 01/22/2014 12:19 AM, Karanbir Singh wrote: >>> On 01/16/2014 04:11 PM, Alessandro Pilotti wrote: >>>> For OpenStack we need 0.7.x. It'll be great if we could have
it in EPEL.
>>>> >>> >>> reporting from a conversation on irc earlier today, Sam is
going to push
>>> getting cloud-init 0.7.x into EPEL-6 within a few days time. >>> >>> that then means we dont need to own cloud-init in
CentOS-Extras/ for
>>> now, and images we ship will retain an upgrade path for the
code/content
>>> inside that. >>> >>> I think its worth waiting for the newer cloud-init to arrive
in epel.
>> >> there is a possibility that we can get 0.7.5 of cloud-init,
which will
>> help resolve a bunch of issues with opennebula and cloudstack
issues as
>> well. > > 0.7.5 is not released upstream yet AFAICT despite their
documentation
> site and other stuff being updated. Can anyone confirm this?
Confirmed. 0.7.5 isn't out yet. 0.7.4 isn't good enough?
0.7.2 should be enough for CloudStack
-sebastien
...Juerg
> The version > that's in ubuntu seems to be built straight from bzr. I've just > committed a pretty large changeset that bumps to 0.7.4; thanks
to Lars
> Kellogg-Stedman and Steve Hardy for their assistance. There are
still
> some dependency issues which I'm working on fixing now, but
those should
> hopefully be taken care of soon. > >> >> > _______________________________________________ > CentOS-devel mailing list > CentOS-devel@centos.org mailto:CentOS-devel@centos.org > http://lists.centos.org/mailman/listinfo/centos-devel _______________________________________________ CentOS-devel mailing list CentOS-devel@centos.org mailto:CentOS-devel@centos.org http://lists.centos.org/mailman/listinfo/centos-devel
CentOS-devel mailing list CentOS-devel@centos.org mailto:CentOS-devel@centos.org http://lists.centos.org/mailman/listinfo/centos-devel
CentOS-devel mailing list CentOS-devel@centos.org mailto:CentOS-devel@centos.org http://lists.centos.org/mailman/listinfo/centos-devel
CentOS-devel mailing list CentOS-devel@centos.org http://lists.centos.org/mailman/listinfo/centos-devel
On Mon, Jan 27, 2014 at 4:14 PM, Sam Kottler s@shk.io wrote:
On 01/27/2014 04:07 PM, Juerg Haefliger wrote:
Hi Sam,
On Sat, Jan 25, 2014 at 2:58 PM, Sam Kottler <s@shk.io mailto:s@shk.io> wrote:
On 01/23/2014 10:49 AM, Sam Kottler wrote:
On 01/23/2014 10:34 AM, Javier Fontan wrote:
For OpenNebula we need at least version 0.7.3.
Great, thanks. So 0.7.4 seems like it'll be okay for all the people
who
requested more recent versions. There are two dependencies which are pending push to EPEL updates; once those are available (tonight's
push)
I will add them as requires to the cloud-init spec and submit an
update.
I've submitted the update: https://admin.fedoraproject.org/updates/cloud-init-0.7.4-1.el6. Auto-karma is disabled because I'd like the opennebula and cloudstack folks specifically to test it, but if you're on EC2/OpenStack or any of the other supported platforms it'd be great to have this tested as
well.
Tested on OpenStack. Missing dependencies:
- python-jsonpatch
- python-oauth
Both of these should be available in EPEL as of late last week. Do you have the repos mirrored locally and haven't updated in a while?
Sorry I wasn't clear enough. Yes, they're available in EPEL but not called out as 'requires' in the cloud-init package.
I also just realized the sudo doesn't work for the cloud-user. It asks for a password. Need to dig around some more.
...Juerg
-S
and cloudinit/source/DataSourceSmartOS.py imports 'serial' (provided by package pyserial) which is not available in EPEL6/CentOS6. We should probably disable this datasource for EPEL6.
The rest looks fine although I didn't do extensive testing.
...Juerg
Thanks and have a great weekend!
-S
Thanks for your patience on this.
-S
On Wed, Jan 22, 2014 at 6:49 PM, sebgoa <runseb@gmail.com
mailto:runseb@gmail.com> wrote:
On Jan 22, 2014, at 6:27 PM, Juerg Haefliger <juergh@gmail.com
mailto:juergh@gmail.com> wrote:
> On Wed, Jan 22, 2014 at 6:12 PM, Sam Kottler <s@shk.io
mailto:s@shk.io> wrote:
>> >> >> >> On 01/22/2014 05:01 PM, Karanbir Singh wrote: >>> On 01/22/2014 12:19 AM, Karanbir Singh wrote: >>>> On 01/16/2014 04:11 PM, Alessandro Pilotti wrote: >>>>> For OpenStack we need 0.7.x. It'll be great if we could have
it in EPEL.
>>>>> >>>> >>>> reporting from a conversation on irc earlier today, Sam is
going to push
>>>> getting cloud-init 0.7.x into EPEL-6 within a few days time. >>>> >>>> that then means we dont need to own cloud-init in
CentOS-Extras/ for
>>>> now, and images we ship will retain an upgrade path for the
code/content
>>>> inside that. >>>> >>>> I think its worth waiting for the newer cloud-init to arrive
in epel.
>>> >>> there is a possibility that we can get 0.7.5 of cloud-init,
which will
>>> help resolve a bunch of issues with opennebula and cloudstack
issues as
>>> well. >> >> 0.7.5 is not released upstream yet AFAICT despite their
documentation
>> site and other stuff being updated. Can anyone confirm this? > > Confirmed. 0.7.5 isn't out yet. 0.7.4 isn't good enough?
0.7.2 should be enough for CloudStack
-sebastien
> > ...Juerg > > >> The version >> that's in ubuntu seems to be built straight from bzr. I've just >> committed a pretty large changeset that bumps to 0.7.4; thanks
to Lars
>> Kellogg-Stedman and Steve Hardy for their assistance. There are
still
>> some dependency issues which I'm working on fixing now, but
those should
>> hopefully be taken care of soon. >> >>> >>> >> _______________________________________________ >> CentOS-devel mailing list >> CentOS-devel@centos.org mailto:CentOS-devel@centos.org >> http://lists.centos.org/mailman/listinfo/centos-devel > _______________________________________________ > CentOS-devel mailing list > CentOS-devel@centos.org mailto:CentOS-devel@centos.org > http://lists.centos.org/mailman/listinfo/centos-devel
CentOS-devel mailing list CentOS-devel@centos.org mailto:CentOS-devel@centos.org http://lists.centos.org/mailman/listinfo/centos-devel
CentOS-devel mailing list CentOS-devel@centos.org mailto:CentOS-devel@centos.org http://lists.centos.org/mailman/listinfo/centos-devel
CentOS-devel mailing list CentOS-devel@centos.org http://lists.centos.org/mailman/listinfo/centos-devel
CentOS-devel mailing list CentOS-devel@centos.org http://lists.centos.org/mailman/listinfo/centos-devel
On 01/27/2014 03:20 PM, Juerg Haefliger wrote:
I also just realized the sudo doesn't work for the cloud-user. It asks for a password. Need to dig around some more.
I am still quite keen to have root as the default user to login as.. Can we have a middle ground where people are able to establsih the requirement for the cloud-user in the metadata for the instance and let cloud-init then do the adduser + append to sudoers ? otherwise, it just falls back to using the root user and injecting key there.
Regards
On Mon, Jan 27, 2014 at 4:42 PM, Karanbir Singh mail-lists@karan.org wrote:
On 01/27/2014 03:20 PM, Juerg Haefliger wrote:
I also just realized the sudo doesn't work for the cloud-user. It asks for a password. Need to dig around some more.
I am still quite keen to have root as the default user to login as.. Can we have a middle ground where people are able to establsih the requirement for the cloud-user in the metadata for the instance and let cloud-init then do the adduser + append to sudoers ? otherwise, it just falls back to using the root user and injecting key there.
Quite frankly I'm not crazy about using 'root' as the default user. I consider it a convenience if there's a non-root default user, otherwise I'd always have to create one myself after logging into an instance. If we want to follow the other distros (ubuntu, fedora), we'd choose 'centos' as the default user. 'cloud-user' is a little Amazon'ish, but I'm biased here :-)
With OpenStack, you can always override cloud-init's behaviour by supplying custom user-data but we should pick a default that makes most sense to users switching from other distros. And in OpenStack's case I would claim that this is 'centos'.
...Juerg
Regards
-- Karanbir Singh +44-207-0999389 | http://www.karan.org/ | twitter.com/kbsingh GnuPG Key : http://www.karan.org/publickey.asc _______________________________________________ CentOS-devel mailing list CentOS-devel@centos.org http://lists.centos.org/mailman/listinfo/centos-devel
On 27.01.2014 15:42, Karanbir Singh wrote:
On 01/27/2014 03:20 PM, Juerg Haefliger wrote:
I also just realized the sudo doesn't work for the cloud-user. It asks for a password. Need to dig around some more.
I am still quite keen to have root as the default user to login as..
Cloudstack traditionally very much relies on the root user being available and functional, as the "root password" (Administrator in windows) is a heavily used feature. We'll need to make sure this will still work. Cloud.cfg in ACS contains: disable_root: 0 ssh_pwauth: 1
Lucian
On 01/27/2014 04:20 PM, Juerg Haefliger wrote:
On Mon, Jan 27, 2014 at 4:14 PM, Sam Kottler <s@shk.io mailto:s@shk.io> wrote:
On 01/27/2014 04:07 PM, Juerg Haefliger wrote:
Hi Sam,
On Sat, Jan 25, 2014 at 2:58 PM, Sam Kottler <s@shk.io mailto:s@shk.io <mailto:s@shk.io mailto:s@shk.io>> wrote:
On 01/23/2014 10:49 AM, Sam Kottler wrote:
On 01/23/2014 10:34 AM, Javier Fontan wrote:
For OpenNebula we need at least version 0.7.3.
Great, thanks. So 0.7.4 seems like it'll be okay for all the
people who
requested more recent versions. There are two dependencies which are pending push to EPEL updates; once those are available (tonight's
push)
I will add them as requires to the cloud-init spec and submit an
update.
I've submitted the update: https://admin.fedoraproject.org/updates/cloud-init-0.7.4-1.el6. Auto-karma is disabled because I'd like the opennebula and cloudstack folks specifically to test it, but if you're on EC2/OpenStack or any of the other supported platforms it'd be great to have this tested as
well.
Tested on OpenStack. Missing dependencies:
- python-jsonpatch
- python-oauth
Both of these should be available in EPEL as of late last week. Do you have the repos mirrored locally and haven't updated in a while?
Sorry I wasn't clear enough. Yes, they're available in EPEL but not called out as 'requires' in the cloud-init package.
You're right. I've submitted another update: https://admin.fedoraproject.org/updates/cloud-init-0.7.4-2.el6. That update only adds python-jsonpatch. It seems like python-oauth is only needed for the MaaS data source - does anyone running RPM-based distros actually end up using that or should we just remove it for now?
I also just realized the sudo doesn't work for the cloud-user. It asks for a password. Need to dig around some more.
...Juerg
-S
and cloudinit/source/DataSourceSmartOS.py imports 'serial' (provided by package pyserial) which is not available in EPEL6/CentOS6. We should probably disable this datasource for EPEL6.
The rest looks fine although I didn't do extensive testing.
...Juerg
Thanks and have a great weekend!
-S
Thanks for your patience on this.
-S
On Wed, Jan 22, 2014 at 6:49 PM, sebgoa <runseb@gmail.com
<mailto:runseb@gmail.com mailto:runseb@gmail.com>> wrote:
> > On Jan 22, 2014, at 6:27 PM, Juerg Haefliger <juergh@gmail.com
<mailto:juergh@gmail.com mailto:juergh@gmail.com>> wrote:
> >> On Wed, Jan 22, 2014 at 6:12 PM, Sam Kottler <s@shk.io
<mailto:s@shk.io mailto:s@shk.io>> wrote:
>>> >>> >>> >>> On 01/22/2014 05:01 PM, Karanbir Singh wrote: >>>> On 01/22/2014 12:19 AM, Karanbir Singh wrote: >>>>> On 01/16/2014 04:11 PM, Alessandro Pilotti wrote: >>>>>> For OpenStack we need 0.7.x. It'll be great if we could have
it in EPEL.
>>>>>> >>>>> >>>>> reporting from a conversation on irc earlier today, Sam is
going to push
>>>>> getting cloud-init 0.7.x into EPEL-6 within a few days time. >>>>> >>>>> that then means we dont need to own cloud-init in
CentOS-Extras/ for
>>>>> now, and images we ship will retain an upgrade path for the
code/content
>>>>> inside that. >>>>> >>>>> I think its worth waiting for the newer cloud-init to arrive
in epel.
>>>> >>>> there is a possibility that we can get 0.7.5 of cloud-init,
which will
>>>> help resolve a bunch of issues with opennebula and cloudstack
issues as
>>>> well. >>> >>> 0.7.5 is not released upstream yet AFAICT despite their
documentation
>>> site and other stuff being updated. Can anyone confirm this? >> >> Confirmed. 0.7.5 isn't out yet. 0.7.4 isn't good enough? > > 0.7.2 should be enough for CloudStack > > -sebastien > > >> >> ...Juerg >> >> >>> The version >>> that's in ubuntu seems to be built straight from bzr. I've just >>> committed a pretty large changeset that bumps to 0.7.4; thanks
to Lars
>>> Kellogg-Stedman and Steve Hardy for their assistance. There are
still
>>> some dependency issues which I'm working on fixing now, but
those should
>>> hopefully be taken care of soon. >>> >>>> >>>> >>> _______________________________________________ >>> CentOS-devel mailing list >>> CentOS-devel@centos.org mailto:CentOS-devel@centos.org
<mailto:CentOS-devel@centos.org mailto:CentOS-devel@centos.org>
>>> http://lists.centos.org/mailman/listinfo/centos-devel >> _______________________________________________ >> CentOS-devel mailing list >> CentOS-devel@centos.org mailto:CentOS-devel@centos.org
<mailto:CentOS-devel@centos.org mailto:CentOS-devel@centos.org>
>> http://lists.centos.org/mailman/listinfo/centos-devel > > _______________________________________________ > CentOS-devel mailing list > CentOS-devel@centos.org mailto:CentOS-devel@centos.org
<mailto:CentOS-devel@centos.org mailto:CentOS-devel@centos.org>
CentOS-devel mailing list CentOS-devel@centos.org mailto:CentOS-devel@centos.org
<mailto:CentOS-devel@centos.org mailto:CentOS-devel@centos.org>
CentOS-devel mailing list CentOS-devel@centos.org mailto:CentOS-devel@centos.org http://lists.centos.org/mailman/listinfo/centos-devel
CentOS-devel mailing list CentOS-devel@centos.org mailto:CentOS-devel@centos.org http://lists.centos.org/mailman/listinfo/centos-devel
CentOS-devel mailing list CentOS-devel@centos.org http://lists.centos.org/mailman/listinfo/centos-devel
We're working quite a bit with MaaS lately, so it's be great to have support for it in the CentOS images as well.
Alessandro
On 27.01.2014, at 18:49, "Sam Kottler" s@shk.io wrote:
On 01/27/2014 04:20 PM, Juerg Haefliger wrote:
On Mon, Jan 27, 2014 at 4:14 PM, Sam Kottler <s@shk.io mailto:s@shk.io> wrote:
On 01/27/2014 04:07 PM, Juerg Haefliger wrote: Hi Sam,
On Sat, Jan 25, 2014 at 2:58 PM, Sam Kottler <s@shk.io mailto:s@shk.io <mailto:s@shk.io mailto:s@shk.io>> wrote:
On 01/23/2014 10:49 AM, Sam Kottler wrote:
> On 01/23/2014 10:34 AM, Javier Fontan wrote: > For OpenNebula we need at least version 0.7.3.
Great, thanks. So 0.7.4 seems like it'll be okay for all the
people who
requested more recent versions. There are two dependencies which are pending push to EPEL updates; once those are available (tonight's
push)
I will add them as requires to the cloud-init spec and submit an
update.
I've submitted the update: https://admin.fedoraproject.org/updates/cloud-init-0.7.4-1.el6. Auto-karma is disabled because I'd like the opennebula and cloudstack folks specifically to test it, but if you're on EC2/OpenStack or any of the other supported platforms it'd be great to have this tested as
well.
Tested on OpenStack. Missing dependencies:
- python-jsonpatch
- python-oauth
Both of these should be available in EPEL as of late last week. Do you have the repos mirrored locally and haven't updated in a while?
Sorry I wasn't clear enough. Yes, they're available in EPEL but not called out as 'requires' in the cloud-init package.
You're right. I've submitted another update: https://admin.fedoraproject.org/updates/cloud-init-0.7.4-2.el6. That update only adds python-jsonpatch. It seems like python-oauth is only needed for the MaaS data source - does anyone running RPM-based distros actually end up using that or should we just remove it for now?
I also just realized the sudo doesn't work for the cloud-user. It asks for a password. Need to dig around some more.
...Juerg
-S
and cloudinit/source/DataSourceSmartOS.py imports 'serial' (provided by package pyserial) which is not available in EPEL6/CentOS6. We should probably disable this datasource for EPEL6.
The rest looks fine although I didn't do extensive testing.
...Juerg
Thanks and have a great weekend!
-S
Thanks for your patience on this.
-S
> > On Wed, Jan 22, 2014 at 6:49 PM, sebgoa <runseb@gmail.com
<mailto:runseb@gmail.com mailto:runseb@gmail.com>> wrote:
>> >> On Jan 22, 2014, at 6:27 PM, Juerg Haefliger <juergh@gmail.com
<mailto:juergh@gmail.com mailto:juergh@gmail.com>> wrote:
>> >>> On Wed, Jan 22, 2014 at 6:12 PM, Sam Kottler <s@shk.io
<mailto:s@shk.io mailto:s@shk.io>> wrote:
>>>> >>>> >>>> >>>>> On 01/22/2014 05:01 PM, Karanbir Singh wrote: >>>>>> On 01/22/2014 12:19 AM, Karanbir Singh wrote: >>>>>>> On 01/16/2014 04:11 PM, Alessandro Pilotti wrote: >>>>>>> For OpenStack we need 0.7.x. It'll be great if we could have
it in EPEL.
>>>>>> >>>>>> reporting from a conversation on irc earlier today, Sam is
going to push
>>>>>> getting cloud-init 0.7.x into EPEL-6 within a few days time. >>>>>> >>>>>> that then means we dont need to own cloud-init in
CentOS-Extras/ for
>>>>>> now, and images we ship will retain an upgrade path for the
code/content
>>>>>> inside that. >>>>>> >>>>>> I think its worth waiting for the newer cloud-init to arrive
in epel.
>>>>> >>>>> there is a possibility that we can get 0.7.5 of cloud-init,
which will
>>>>> help resolve a bunch of issues with opennebula and cloudstack
issues as
>>>>> well. >>>> >>>> 0.7.5 is not released upstream yet AFAICT despite their
documentation
>>>> site and other stuff being updated. Can anyone confirm this? >>> >>> Confirmed. 0.7.5 isn't out yet. 0.7.4 isn't good enough? >> >> 0.7.2 should be enough for CloudStack >> >> -sebastien >> >> >>> >>> ...Juerg >>> >>> >>>> The version >>>> that's in ubuntu seems to be built straight from bzr. I've just >>>> committed a pretty large changeset that bumps to 0.7.4; thanks
to Lars
>>>> Kellogg-Stedman and Steve Hardy for their assistance. There are
still
>>>> some dependency issues which I'm working on fixing now, but
those should
>>>> hopefully be taken care of soon. >>>> >>>> _______________________________________________ >>>> CentOS-devel mailing list >>>> CentOS-devel@centos.org mailto:CentOS-devel@centos.org
<mailto:CentOS-devel@centos.org mailto:CentOS-devel@centos.org>
>>>> http://lists.centos.org/mailman/listinfo/centos-devel >>> _______________________________________________ >>> CentOS-devel mailing list >>> CentOS-devel@centos.org mailto:CentOS-devel@centos.org
<mailto:CentOS-devel@centos.org mailto:CentOS-devel@centos.org>
>>> http://lists.centos.org/mailman/listinfo/centos-devel >> >> _______________________________________________ >> CentOS-devel mailing list >> CentOS-devel@centos.org mailto:CentOS-devel@centos.org
<mailto:CentOS-devel@centos.org mailto:CentOS-devel@centos.org>
CentOS-devel mailing list CentOS-devel@centos.org mailto:CentOS-devel@centos.org
<mailto:CentOS-devel@centos.org mailto:CentOS-devel@centos.org>
CentOS-devel mailing list CentOS-devel@centos.org mailto:CentOS-devel@centos.org http://lists.centos.org/mailman/listinfo/centos-devel
CentOS-devel mailing list CentOS-devel@centos.org mailto:CentOS-devel@centos.org http://lists.centos.org/mailman/listinfo/centos-devel
CentOS-devel mailing list CentOS-devel@centos.org http://lists.centos.org/mailman/listinfo/centos-devel
CentOS-devel mailing list CentOS-devel@centos.org http://lists.centos.org/mailman/listinfo/centos-devel
-
Alan Pevec -
Alessandro Pilotti -
Javier Fontan -
Juerg Haefliger -
Karanbir Singh -
Lars Kellogg-Stedman -
Logan McNaughton -
Nux! -
Sam Kottler -
Sebastien Goasguen -
sebgoa