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