9:56 a.m.
Used the Quickstart and just swapped out havana for grizzly, but
otherwise followed the Quickstart verbatim
A few things I've noticed...
RDO Grizzly has: openstack-packstack-2013.1.1-0.22.dev653.el6.src.rpm
RDO Havana has: openstack-packstack-2013.2.1-0.1.dev691.el6.src.rpm
It's hard to tell which version of packstack is 'newer' because the
2013.2.1 vs. 2013.1.1 makes the Havana one automatically > wrt NVR, even
if the tarball behind the RPM is older.
Is the devXXX number indicative of the tarball release? If this is the
case, then havana does have a later version which makes sense.
But... what I noticed is that running packstack from Havana RDO repos
doesn't create the demo tenant or import the cirros image (which I
thought should happen for all --allinone style installs)
Then I thought to check the nightly repos here:
http://repos.fedorapeople.org/repos/openstack/openstack-trunk/el6/x86_64/
Packstack isn't even in those repos, which means that folks can't use
packstack to install nightly builds easily.
All that being said, once I manually imported the cirros image, and used
the admin tenant, I was able to boot an instance. But, I did notice
that the Horizon UI acted a little differently. I didn't see dynamic
refreshing of the instance state and the little progress bar anymore. I
also can't seem to click on the "More" button to do things like launch
the VNC Console or Associate a Floating IP. In various screens, the
"Edit" or "Launch" buttons work fine. But on the screens with a
"More"
drop down button, the drop down doesn't pop up and so I can't take any
of those actions. (I tried this in both Chrome and Firefox on F19, both
had the same issue)
Of course, this was all with Nova Networking, not Neutron, since we
don't have neutron in the RDO Havana nightly or milestone repos yet.
It'll be nice to verify that Neutron allinone works for Havana as well,
as soon as we get the packages ready from the renaming. (Of course,
this means also need the Puppet modules and Packstack changes for
renaming as well)
So, checklist:
* packstack in Havana needs to create demo tenant and import cirros
image just like in RDO Grizzly
* Horizon seems to have screen refresh/updates and More button issues
* Need Neutron packages for Havana so that we can use Neutron in Havana
* Need Packstack available so that RDO Nightly users can install the
nightly builds
Cheers,
Perry
6:05 a.m.
On 04/08/13 16:56, Perry Myers wrote:
So, checklist:
* packstack in Havana needs to create demo tenant and import cirros
image just like in RDO Grizzly
* Horizon seems to have screen refresh/updates and More button issues
* Need Neutron packages for Havana so that we can use Neutron in Havana
* Need Packstack available so that RDO Nightly users can install the
nightly builds
Perry,
sadly I was unable to install via packstack for several due several
issues, so I can not reproduce your issue.
One thing I mentioned for Havana is, we require a newer version of
python-django-compressor:
http://kojipkgs.fedoraproject.org//packages/python-django-compressor/1.3/...
Does that change the behaviour of Horizon in your install?
yum localinstall ... && service httpd restart
Matthias
8:52 a.m.
On 08/06/2013 07:05 AM, Matthias Runge wrote:
On 04/08/13 16:56, Perry Myers wrote:
>
> So, checklist:
>
> * packstack in Havana needs to create demo tenant and import cirros
> image just like in RDO Grizzly
> * Horizon seems to have screen refresh/updates and More button issues
> * Need Neutron packages for Havana so that we can use Neutron in Havana
> * Need Packstack available so that RDO Nightly users can install the
> nightly builds
Perry,
sadly I was unable to install via packstack for several due several
issues, so I can not reproduce your issue.
One thing I mentioned for Havana is, we require a newer version of
python-django-compressor:
http://kojipkgs.fedoraproject.org//packages/python-django-compressor/1.3/...
Does that change the behaviour of Horizon in your install?
yum localinstall ... && service httpd restart
I'll try this when I get a chance, but a few questions...
If this is required for Horizon, why is it not listed with an explicit
Requires in the spec file?
If it's required for Horizon, why is the package not installed right now
when I install RDO Havana milestone 2?
If the package just hasn't hit EPEL yet, we should be carrying it in RDO
repos explicitly until it does hit EPEL
Pádraig, can you work with Matthias to resolve this?
Perry
10:52 a.m.
On 08/06/2013 02:52 PM, Perry Myers wrote:
On 08/06/2013 07:05 AM, Matthias Runge wrote:
> On 04/08/13 16:56, Perry Myers wrote:
>>
>> So, checklist:
>>
>> * packstack in Havana needs to create demo tenant and import cirros
>> image just like in RDO Grizzly
>> * Horizon seems to have screen refresh/updates and More button issues
>> * Need Neutron packages for Havana so that we can use Neutron in Havana
>> * Need Packstack available so that RDO Nightly users can install the
>> nightly builds
> Perry,
>
> sadly I was unable to install via packstack for several due several
> issues, so I can not reproduce your issue.
>
> One thing I mentioned for Havana is, we require a newer version of
> python-django-compressor:
>
http://kojipkgs.fedoraproject.org//packages/python-django-compressor/1.3/...
>
> Does that change the behaviour of Horizon in your install?
> yum localinstall ... && service httpd restart
I'll try this when I get a chance, but a few questions...
If this is required for Horizon, why is it not listed with an explicit
Requires in the spec file?
It's best to avoid explicit versions if possible.
It adds a maintenance burden/cruft and might preclude
using otherwise OK older versions with backports on some systems.
If it's required for Horizon, why is the package not installed
right now
when I install RDO Havana milestone 2?
I presume more testing is required.
I see the updated el6-havana version was just built today.
I did a quick test. The package installed without issue,
and horizon seems to work without issue with basic tests,
so I've now added this to the havana el6 repo
(the fedora 19 version of this package is already
at 1.3 in the Fedora repos).
If the package just hasn't hit EPEL yet, we should be carrying it
in RDO
repos explicitly until it does hit EPEL
I'm not sure that epel-6 can be updated due to
explicit requires on Django14. Well more accurately
it might benefit from an update, but would probably
need to be a separate package for epel-6 and rdo-havana
thanks,
Pádraig.
2:50 a.m.
On 06/08/13 17:52, Pádraig Brady wrote:
I'm not sure that epel-6 can be updated due to
explicit requires on Django14. Well more accurately
it might benefit from an update, but would probably
need to be a separate package for epel-6 and rdo-havana
imho
python-django-compressor-1.3 is not 100% backwards compatible to
python-django-compressor-1.2
Django14 is the only Django version in EPEL right now.
Matthias
2:46 a.m.
On 06/08/13 15:52, Perry Myers wrote:
I'll try this when I get a chance, but a few questions...
If this is required for Horizon, why is it not listed with an explicit
Requires in the spec file?
If it's required for Horizon, why is the package not installed right now
when I install RDO Havana milestone 2?
you got an older version from EPEL.
Using explicit requires (including version numbers is discouraged).
So the question is: why wasn't the newer version included in the RDO
repo: I can't answer that, it was just forgotten. The same is also true
for e.g python-keystoneclient in a updated version.
If the package just hasn't hit EPEL yet, we should be carrying it in RDO
repos explicitly until it does hit EPEL
python-django-compressor-1.2 is in EPEL for nearly 10 months now. Still,
the version from EPEL is too old; sadly, I can not simply upgrade it.
Matthias
3:40 a.m.
On Aug 4, 2013, at 4:56 PM, Perry Myers <pmyers(a)redhat.com> wrote:
Then I thought to check the nightly repos here:
http://repos.fedorapeople.org/repos/openstack/openstack-trunk/el6/x86_64/
Packstack isn't even in those repos, which means that folks can't use
packstack to install nightly builds easily.
This is something the CI team discussed last Monday. SmokeStack ought to pack Packstack
along the rest of the components. Testing it may be out of scope, but at least it should
generate the PackStack RPM. It'd avoid the problem you just described so people could
test the very latest version of all the packages with ease.
It's a work item for this week, so we should get it sorted out within the next few
days.
All the best,
Alvaro
5:25 a.m.
On 08/07/2013 09:40 AM, Alvaro Lopez Ortega wrote:
On Aug 4, 2013, at 4:56 PM, Perry Myers <pmyers(a)redhat.com
<mailto:pmyers@redhat.com>> wrote:
> Then I thought to check the nightly repos here:
> http://repos.fedorapeople.org/repos/openstack/openstack-trunk/el6/x86_64/
>
> Packstack isn't even in those repos, which means that folks can't use
> packstack to install nightly builds easily.
This is something the CI team discussed last Monday. SmokeStack ought to pack Packstack
along the rest of the components. Testing it may be out of scope, but at least it should
generate the PackStack RPM. It'd avoid the problem you just described so people could
test the very latest version of all the packages with ease.
It's a work item for this week, so we should get it sorted out within the next few
days.
All the best,
Alvaro
What I had previously suggested was that the trunk packages were just updates
on top of the existing pre-release standard repo.
So to test the trunk repo you would currently enable for example
the Havana milestone repo _and_ the trunk repo,
and in that way get all the ancillary packages without the
space and maintenance overhead of keeping two very similar repos in sync.
thanks,
Pádraig.
8:42 a.m.
On 08/07/2013 06:25 AM, Pádraig Brady wrote:
On 08/07/2013 09:40 AM, Alvaro Lopez Ortega wrote:
> On Aug 4, 2013, at 4:56 PM, Perry Myers <pmyers(a)redhat.com
<mailto:pmyers@redhat.com>> wrote:
>
>> Then I thought to check the nightly repos here:
>> http://repos.fedorapeople.org/repos/openstack/openstack-trunk/el6/x86_64/
>>
>> Packstack isn't even in those repos, which means that folks can't use
>> packstack to install nightly builds easily.
>
> This is something the CI team discussed last Monday. SmokeStack ought to pack
Packstack along the rest of the components. Testing it may be out of scope, but at least
it should generate the PackStack RPM. It'd avoid the problem you just described so
people could test the very latest version of all the packages with ease.
>
> It's a work item for this week, so we should get it sorted out within the next
few days.
>
> All the best,
> Alvaro
What I had previously suggested was that the trunk packages were just updates
on top of the existing pre-release standard repo.
So to test the trunk repo you would currently enable for example
the Havana milestone repo _and_ the trunk repo,
and in that way get all the ancillary packages without the
space and maintenance overhead of keeping two very similar repos in sync.
+1, this is a good idea
Do we need a release RPM though that makes getting the combination of
nightly + stable repos enabled simultaneously?
Perry
8:48 a.m.
----- Original Message -----
From: "Perry Myers" <pmyers(a)redhat.com>
To: "Pádraig Brady" <pbrady(a)redhat.com>
Cc: "Alvaro Lopez Ortega" <aortega(a)redhat.com>, "rdo-list"
redhat.com>, "Dan Prince" <dprince(a)redhat.com>
Sent: Wednesday, August 7, 2013 9:42:16 AM
Subject: Re: [Rdo-list] experiences trying out RDO Havana (H2 milestone) on RHEL 6.4
On 08/07/2013 06:25 AM, Pádraig Brady wrote:
> On 08/07/2013 09:40 AM, Alvaro Lopez Ortega wrote:
>> On Aug 4, 2013, at 4:56 PM, Perry Myers <pmyers(a)redhat.com
>> <mailto:pmyers@redhat.com>> wrote:
>>
>>> Then I thought to check the nightly repos here:
>>> http://repos.fedorapeople.org/repos/openstack/openstack-trunk/el6/x86_64/
>>>
>>> Packstack isn't even in those repos, which means that folks can't
use
>>> packstack to install nightly builds easily.
>>
>> This is something the CI team discussed last Monday. SmokeStack ought to
>> pack Packstack along the rest of the components. Testing it may be out of
>> scope, but at least it should generate the PackStack RPM. It'd avoid the
>> problem you just described so people could test the very latest version
>> of all the packages with ease.
>>
>> It's a work item for this week, so we should get it sorted out within the
>> next few days.
>>
>> All the best,
>> Alvaro
>
> What I had previously suggested was that the trunk packages were just
> updates
> on top of the existing pre-release standard repo.
> So to test the trunk repo you would currently enable for example
> the Havana milestone repo _and_ the trunk repo,
> and in that way get all the ancillary packages without the
> space and maintenance overhead of keeping two very similar repos in sync.
+1, this is a good idea
Do we need a release RPM though that makes getting the combination of
nightly + stable repos enabled simultaneously?
Perry
Probably that and a page on the wiki, linked in from the QuickStart (similar to how the
"get fedora" page has a little note when alpha/beta versions are available),
making the information discoverable for users wanting to try Havana packages.
Thanks,
Steve
8:57 a.m.
On 08/07/2013 02:42 PM, Perry Myers wrote:
On 08/07/2013 06:25 AM, Pádraig Brady wrote:
> On 08/07/2013 09:40 AM, Alvaro Lopez Ortega wrote:
>> On Aug 4, 2013, at 4:56 PM, Perry Myers <pmyers(a)redhat.com
<mailto:pmyers@redhat.com>> wrote:
>>
>>> Then I thought to check the nightly repos here:
>>> http://repos.fedorapeople.org/repos/openstack/openstack-trunk/el6/x86_64/
>>>
>>> Packstack isn't even in those repos, which means that folks can't
use
>>> packstack to install nightly builds easily.
>>
>> This is something the CI team discussed last Monday. SmokeStack ought to pack
Packstack along the rest of the components. Testing it may be out of scope, but at least
it should generate the PackStack RPM. It'd avoid the problem you just described so
people could test the very latest version of all the packages with ease.
>>
>> It's a work item for this week, so we should get it sorted out within the
next few days.
>>
>> All the best,
>> Alvaro
>
> What I had previously suggested was that the trunk packages were just updates
> on top of the existing pre-release standard repo.
> So to test the trunk repo you would currently enable for example
> the Havana milestone repo _and_ the trunk repo,
> and in that way get all the ancillary packages without the
> space and maintenance overhead of keeping two very similar repos in sync.
+1, this is a good idea
Do we need a release RPM though that makes getting the combination of
nightly + stable repos enabled simultaneously?
Probably should include the nightly repo info
in the Havana+ rdo-release.rpm, but disabled.
Then it can be a documented step to do this before packstack/foreman ...
sudo crudini --set /etc/yum.repos.d/rdo-release.repo rdo-nightly enabled 1
thanks,
Pádraig.
9:46 p.m.
On 08/07/2013 09:42 AM, Perry Myers wrote:
On 08/07/2013 06:25 AM, Pádraig Brady wrote:
> On 08/07/2013 09:40 AM, Alvaro Lopez Ortega wrote:
>> On Aug 4, 2013, at 4:56 PM, Perry Myers <pmyers(a)redhat.com
<mailto:pmyers@redhat.com>> wrote:
>>
>>> Then I thought to check the nightly repos here:
>>> http://repos.fedorapeople.org/repos/openstack/openstack-trunk/el6/x86_64/
>>>
>>> Packstack isn't even in those repos, which means that folks can't
use
>>> packstack to install nightly builds easily.
>>
>> This is something the CI team discussed last Monday. SmokeStack ought to pack
Packstack along the rest of the components. Testing it may be out of scope, but at least
it should generate the PackStack RPM. It'd avoid the problem you just described so
people could test the very latest version of all the packages with ease.
>>
>> It's a work item for this week, so we should get it sorted out within the
next few days.
>>
>> All the best,
>> Alvaro
>
> What I had previously suggested was that the trunk packages were just updates
> on top of the existing pre-release standard repo.
> So to test the trunk repo you would currently enable for example
> the Havana milestone repo _and_ the trunk repo,
> and in that way get all the ancillary packages without the
> space and maintenance overhead of keeping two very similar repos in sync.
+1, this is a good idea
Do we need a release RPM though that makes getting the combination of
nightly + stable repos enabled simultaneously?
I chatted with apevec with this and we came to conclusion that a release
rpm isn't needed... what we do need to do is take this repo file:
http://repos.fedorapeople.org/repos/openstack/openstack-trunk/el6-opensta...
Right now it just has:
# Place this file in your /etc/yum.repos.d/ directory
[el6-openstack-trunk]
name=Openstack Upstream Repository for EL6
baseurl=http://repos.fedorapeople.org/repos/openstack/openstack-trunk/el6...
enabled=1
skip_if_unavailable=1
gpgcheck=0
priority=98
But we need to add to that repo file an additional repo:
[openstack-havana]
name=OpenStack Havana Repository for EPEL 6
baseurl=http://repos.fedorapeople.org/repos/openstack/openstack-havana/ep...
enabled=1
skip_if_unavailable=0
gpgcheck=0
priority=98
That way when you grab the nightly repo file, you would get packstack
from the openstack-havana repo and other base packages like kernel, etc.
But then the nightly openstack specific RPMs would come from the
nightly repo.
Alan, can you make this change tomorrow?
Perry
7:03 a.m.
On 08/14/2013 05:31 AM, Alan Pevec wrote:
> Alan, can you make this change tomorrow?
I did that already yesterday, but looks like FPO has aggressive caching - you might need
shift-ctrl-R to get a fresh copy.
Indeed. Thanks, it looks right now!
Though, should openstack-havana have priority=98 though?
Perry
12:02 p.m.
On 14/08/13 14:49, Alan Pevec wrote:
> Though, should openstack-havana have priority=98 though?
No, we should get rid of yum-prio in RDO, it should win with higher NVRs instead.
The only reason could be python-django 1.4 issue we had but I think horizon spec was
fixed in the meantime, Matthias?
Cheers,
Alan
Better, I deprecated and retired Django, so there's just only one left
(Django14).
Matthias
9:01 a.m.
On 08/07/2013 04:40 AM, Alvaro Lopez Ortega wrote:
This is something the CI team discussed last Monday. SmokeStack ought
to pack Packstack along the rest of the components. Testing it may be
out of scope, but at least it should generate the PackStack RPM. It'd
avoid the problem you just described so people could test the very
latest version of all the packages with ease.
Would this also reduce the three step QuickStart to two steps? (i.e., no
need to install packstack as a separate step 2.)
--
Rich Bowen
OpenStack Community Liaison
http://openstack.redhat.com/
9:05 a.m.
On 08/07/2013 03:01 PM, Rich Bowen wrote:
On 08/07/2013 04:40 AM, Alvaro Lopez Ortega wrote:
>
> This is something the CI team discussed last Monday. SmokeStack ought to pack
Packstack along the rest of the components. Testing it may be out of scope, but at least
it should generate the PackStack RPM. It'd avoid the problem you just described so
people could test the very latest version of all the packages with ease.
Would this also reduce the three step QuickStart to two steps? (i.e., no need to install
packstack as a separate step 2.)
I don't think so due to catch 22.
You need to install the repo rpm without other deps first,
to make the repo available to yum.
Only then can you install packages from that repo
(that may depend on other packages within that repo)
cheers,
Pádraig.
9:49 p.m.
* packstack in Havana needs to create demo tenant and import cirros
image just like in RDO Grizzly
Done!
* Horizon seems to have screen refresh/updates and More button issues
Resolved!
* Need Neutron packages for Havana so that we can use Neutron in
Havana
Done!
* Need Packstack available so that RDO Nightly users can install the
nightly builds
This is still pending, and being discussed w/ apevec on other branch of
this thread
4127
days inactive
4137
days old
18 comments
7 participants
participants (7)
-
Alan Pevec -
Alvaro Lopez Ortega -
Matthias Runge -
Perry Myers -
Pádraig Brady -
Rich Bowen -
Steve Gordon