[Rdo-list] Reminder: The Mitaka trunk repositories have been "branched" in preparation for stable release
1:46 p.m.
Hi,
This is just a reminder that, as the release of Mitaka draws near and
the stable/mitaka branches have started appearing upstream, we have
also "branched" Mitaka.
http://trunk.rdoproject.org/centos7 (or
http://trunk.rdoproject.org/centos7-master) has been Newton for around
two weeks now and is entirely untested by the RDO CI at this time.
If you were previously installing from repositories like:
- http://trunk.rdoproject.org/centos7/delorean-deps.repo
- http://trunk.rdoproject.org/centos7/current-passed-ci/delorean.repo
Please transition to:
- http://trunk.rdoproject.org/centos7-mitaka/delorean-deps.repo
- http://trunk.rdoproject.org/centos7-mitaka/delorean.repo.
Since Newton is still untested, things are bound to break and stop working.
As such, please use the Mitaka if you'd like to test the upcoming
release of OpenStack.
Please note that the rdo-release repository RPM is still based on
Liberty as Mitaka has not yet been released upstream.
The anticipated _upstream_ release date for Mitaka is on April 7th [1].
As usual, all of our efforts are currently aimed at doing the general
availability of the RDO stable release of Mitaka as soon as possible.
Our target is to release within 1 week of the upstream stable announcement.
Let us know if you have any questions !
[1]: http://releases.openstack.org/mitaka/index.html
David Moreau Simard
Senior Software Engineer | Openstack RDO
dmsimard = [irc, github, twitter]
3:08 p.m.
________________________________________
From: rdo-list-bounces(a)redhat.com <rdo-list-bounces(a)redhat.com> on behalf of David
Moreau Simard <dms(a)redhat.com>
Sent: Wednesday, March 23, 2016 2:46 PM
To: rdo-list
Subject: [Rdo-list] Reminder: The Mitaka trunk repositories have been "branched"
in preparation for stable release
Hi,
This is just a reminder that, as the release of Mitaka draws near and
the stable/mitaka branches have started appearing upstream, we have
also "branched" Mitaka.
http://trunk.rdoproject.org/centos7 (or
http://trunk.rdoproject.org/centos7-master) has been Newton for around
two weeks now and is entirely untested by the RDO CI at this time.
If you were previously installing from repositories like:
- http://trunk.rdoproject.org/centos7/delorean-deps.repo
- http://trunk.rdoproject.org/centos7/current-passed-ci/delorean.repo
Please transition to:
- http://trunk.rdoproject.org/centos7-mitaka/delorean-deps.repo
- http://trunk.rdoproject.org/centos7-mitaka/delorean.repo.
At the moment delorean.repo doesn't exist in
http://trunk.rdoproject.org/centos7-mitaka/
Mentioned file is in https://trunk.rdoproject.org/centos7-mitaka/current-passed-ci/
Thanks.
Boris.
Since Newton is still untested, things are bound to break and stop
working.
As such, please use the Mitaka if you'd like to test the upcoming
release of
OpenStack.
Please note that the rdo-release repository RPM is still based on
Liberty as Mitaka has not yet been released upstream.
The anticipated _upstream_ release date for Mitaka is on April 7th [1].
As usual, all of our efforts are currently aimed at doing the general
availability of the RDO stable release of Mitaka as soon as possible.
Our target is to release within 1 week of the upstream stable announcement.
Let us know if you have any questions !
[1]: http://releases.openstack.org/mitaka/index.html
David Moreau Simard
Senior Software Engineer | Openstack RDO
dmsimard = [irc, github, twitter]
_______________________________________________
Rdo-list mailing list
Rdo-list(a)redhat.com
https://www.redhat.com/mailman/listinfo/rdo-list
To unsubscribe: rdo-list-unsubscribe(a)redhat.com
3:24 p.m.
On Wed, Mar 23, 2016 at 4:08 PM, Boris Derzhavets
<bderzhavets(a)hotmail.com> wrote:
At the moment delorean.repo doesn't exist in
http://trunk.rdoproject.org/centos7-mitaka/
Mentioned file is in https://trunk.rdoproject.org/centos7-mitaka/current-passed-ci/
Indeed. Typo. Thanks for correcting me :)
David Moreau Simard
Senior Software Engineer | Openstack RDO
dmsimard = [irc, github, twitter]
6:24 a.m.
New subject: [Rdo-list] What magnum status in RDO Mitaka is supposed to be ?
Actually, my question is :-
Due to I cannot find any RH's docs magnum related on the Net,
I am under impression that magnum is only for RHOS 9.
Am I correct ? ( I realize that profit would be always the major concern, so no complaints
)
Nova-Docker, stable branch has been checked out for driver build, doesn't
seem to support FIPs ( just pinging works) been installed on RDO Mitaka ( build 20160322
)
Compute Node.
Thank you.
Boris.
8:10 a.m.
New subject: [Rdo-list] What magnum status in RDO Mitaka is supposed to be ?
Due to I cannot find any RH's docs magnum related on the Net,
I am under impression that magnum is only for RHOS 9.
Am I correct ? ( I realize that profit would be always the major concern, so no
complaints )
Package being in RDO is necessary but NOT sufficient to be present in
the next OSP product version, same as package in Fedora doesn't mean it
will be included in the next RHEL. Product content is defined by Red Hat
product management, which I'm not part of.
Nova-Docker, stable branch has been checked out for driver build,
doesn't
seem to support FIPs ( just pinging works) been installed on RDO Mitaka ( build 20160322
)
Compute Node.
I'm also clueless about Magnum, so I'll defer answering that to the
magnum maintainers in RDO:
$ rdopkg info openstack-magnum
...
maintainers:
- chkumar(a)redhat.com
- mathieu.velten(a)cern.ch
Cheers,
Alan
1:58 a.m.
New subject: [Rdo-list] What magnum status in RDO Mitaka is supposed to be ?
________________________________________
From: Alan Pevec <alan.pevec(a)redhat.com>
Sent: Thursday, March 24, 2016 9:10 AM
To: Boris Derzhavets; rdo-list
Subject: Re: [Rdo-list] What magnum status in RDO Mitaka is supposed to be ?
Due to I cannot find any RH's docs magnum related on the Net,
I am under impression that magnum is only for RHOS 9.
Am I correct ? ( I realize that profit would be always the major concern, so no
complaints )
Package being in RDO is necessary but NOT sufficient to be present in
the next OSP product version, same as package in Fedora doesn't mean it
will be included in the next RHEL. Product content is defined by Red Hat
product management, which I'm not part of.
Nova-Docker, stable branch has been checked out for driver build,
doesn't
seem to support FIPs ( just pinging works) been installed on RDO Mitaka ( build 20160322
)
Compute Node.
I>'m also clueless about Magnum, so I'll defer answering that to the
magnum maintainers in RDO:
$ rdopkg info openstack-magnum
Per https://wiki.openstack.org/wiki/Magnum
Magnum uses Heat to orchestrate an OS image which contains Docker and Kubernetes and runs
that image in either virtual machines or bare metal in a cluster configuration. Click
below for a 5 minute demo of how Magnum works.
...
maintainers:
- chkumar(a)redhat.com
- mathieu.velten(a)cern.ch
Cheers,
Alan
11:17 a.m.
New subject: [Rdo-list] What magnum status in RDO Mitaka is supposed to be ?
I attempted manual magnum set up in general updating git checkouts from
Magnum in RDO OpenStack – Liberty Manual Installation from source code :-
http://egonzalez.org/magnum-in-rdo-openstack-liberty-manual-installation-...
I was able start services after rebuild
openstack-magnum-2.0.1-0.20160324110644.c0c2bdb.el7.centos.src.rpm,
which passed CI with build 20160324
Finally I was hit by known bug
http://osdir.com/ml/openstack-dev/2016-02/msg02123.html.
It is possible to run suggested scripts, but I guess keystone v3 is required to get
things done on RDO Mitaka.
In meantime :-
[root@ip-192-169-142-127 ~(keystone_admin)]# nova-manage version
13.0.0-0.20160324111850.803171f.el7.centos
[root@ip-192-169-142-127 ~(keystone_admin)]# keystone endpoint-list | grep 5000
| 43e01cdd87934c4faa7c016fa29c0c69 | RegionOne | http://192.169.142.127:5000/v2.0
| http://192.169.142.127:5000/v2.0 |
http://192.169.142.127:35357/v2.0 | 70d1e7ad70544601a288e42b2f29181a |
[root@ip-192-169-142-127 ~(keystone_admin)]# rpm -qa \*keystone\*
python-keystoneclient-2.3.2-0.20160318012243.92741ad.el7.centos.noarch
python-keystonemiddleware-4.3.1-0.20160324202909.a0a1e4f.el7.centos.noarch
openstack-keystone-9.0.0.0-0.20160325103215.aa53ad9.el7.centos.noarch
python2-keystoneauth1-2.3.1-0.20160324204310.63267fa.el7.centos.noarch
python-keystone-9.0.0.0-0.20160325103215.aa53ad9.el7.centos.noarch
I guess still RDO Mitaka stays with keystone v2.0 upstream version of magnum for Mitaka
won't be available.
My last question is :-
as far as
http://egonzalez.org/magnum-in-rdo-openstack-liberty-manual-installation-...
works why packaging is not done for RDO Liberty
Thank you.
Boris.
________________________________________
From: rdo-list-bounces(a)redhat.com <rdo-list-bounces(a)redhat.com> on behalf of Boris
Derzhavets <bderzhavets(a)hotmail.com>
Sent: Sunday, March 27, 2016 2:58 AM
To: rdo-list
Subject: Re: [Rdo-list] What magnum status in RDO Mitaka is supposed to be ?
________________________________________
From: Alan Pevec <alan.pevec(a)redhat.com>
Sent: Thursday, March 24, 2016 9:10 AM
To: Boris Derzhavets; rdo-list
Subject: Re: [Rdo-list] What magnum status in RDO Mitaka is supposed to be ?
Due to I cannot find any RH's docs magnum related on the Net,
I am under impression that magnum is only for RHOS 9.
Am I correct ? ( I realize that profit would be always the major concern, so no
complaints )
Package being in RDO is necessary but NOT sufficient to be present in
the next OSP product version, same as package in Fedora doesn't mean it
will be included in the next RHEL. Product content is defined by Red Hat
product management, which I'm not part of.
Nova-Docker, stable branch has been checked out for driver build,
doesn't
seem to support FIPs ( just pinging works) been installed on RDO Mitaka ( build 20160322
)
Compute Node.
I>'m also clueless about Magnum, so I'll defer answering that to the
magnum maintainers in RDO:
$ rdopkg info openstack-magnum
Per https://wiki.openstack.org/wiki/Magnum
Magnum uses Heat to orchestrate an OS image which contains Docker and Kubernetes and runs
that image in either virtual machines or bare metal in a cluster configuration. Click
below for a 5 minute demo of how Magnum works.
...
maintainers:
- chkumar(a)redhat.com
- mathieu.velten(a)cern.ch
Cheers,
Alan
_______________________________________________
Rdo-list mailing list
Rdo-list(a)redhat.com
https://www.redhat.com/mailman/listinfo/rdo-list
To unsubscribe: rdo-list-unsubscribe(a)redhat.com
3:51 p.m.
New subject: [Rdo-list] What magnum status in RDO Mitaka is supposed to be ?
________________________________________
From: rdo-list-bounces(a)redhat.com <rdo-list-bounces(a)redhat.com> on behalf of Boris
Derzhavets <bderzhavets(a)hotmail.com>
Sent: Sunday, March 27, 2016 12:17 PM
To: chkumar(a)redhat.com; rdo-list
Subject: Re: [Rdo-list] What magnum status in RDO Mitaka is supposed to be ?
I attempted manual magnum set up in general updating git checkouts from
Magnum in RDO OpenStack – Liberty Manual Installation from source code :-
http://egonzalez.org/magnum-in-rdo-openstack-liberty-manual-installation-...
I was able start services after rebuild
openstack-magnum-2.0.1-0.20160324110644.c0c2bdb.el7.centos.src.rpm,
which passed CI with build 20160324
Finally I was hit by known bug
http://osdir.com/ml/openstack-dev/2016-02/msg02123.html.
It is possible to run suggested scripts, but I guess keystone v3 is required to get
things done on RDO Mitaka.
In meantime :-
[root@ip-192-169-142-127 ~(keystone_admin)]# nova-manage version
13.0.0-0.20160324111850.803171f.el7.centos
[root@ip-192-169-142-127 ~(keystone_admin)]# keystone endpoint-list | grep 5000
| 43e01cdd87934c4faa7c016fa29c0c69 | RegionOne | http://192.169.142.127:5000/v2.0
| http://192.169.142.127:5000/v2.0 |
http://192.169.142.127:35357/v2.0 | 70d1e7ad70544601a288e42b2f29181a |
[root@ip-192-169-142-127 ~(keystone_admin)]# rpm -qa \*keystone\*
python-keystoneclient-2.3.2-0.20160318012243.92741ad.el7.centos.noarch
python-keystonemiddleware-4.3.1-0.20160324202909.a0a1e4f.el7.centos.noarch
openstack-keystone-9.0.0.0-0.20160325103215.aa53ad9.el7.centos.noarch
python2-keystoneauth1-2.3.1-0.20160324204310.63267fa.el7.centos.noarch
python-keystone-9.0.0.0-0.20160325103215.aa53ad9.el7.centos.noarch
I guess still RDO Mitaka stays with keystone v2.0 upstream version of magnum for Mitaka
won't be available.
My last question is :-
as far as
http://egonzalez.org/magnum-in-rdo-openstack-liberty-manual-installation-...
works why packaging is not done for RDO Liberty
Maybe it's done in https://trunk.rdoproject.org/centos7-liberty/current-passed-ci/
openstack-magnum-1.0.0.0b2-0.20160211160358.fa7814e.el7.centos.src.rpm 2016-02-11 16:04
455K
Thank you.
Boris.
________________________________________
From: rdo-list-bounces(a)redhat.com <rdo-list-bounces(a)redhat.com> on behalf of Boris
Derzhavets <bderzhavets(a)hotmail.com>
Sent: Sunday, March 27, 2016 2:58 AM
To: rdo-list
Subject: Re: [Rdo-list] What magnum status in RDO Mitaka is supposed to be ?
________________________________________
From: Alan Pevec <alan.pevec(a)redhat.com>
Sent: Thursday, March 24, 2016 9:10 AM
To: Boris Derzhavets; rdo-list
Subject: Re: [Rdo-list] What magnum status in RDO Mitaka is supposed to be ?
Due to I cannot find any RH's docs magnum related on the Net,
I am under impression that magnum is only for RHOS 9.
Am I correct ? ( I realize that profit would be always the major concern, so no
complaints )
Package being in RDO is necessary but NOT sufficient to be present in
the next OSP product version, same as package in Fedora doesn't mean it
will be included in the next RHEL. Product content is defined by Red Hat
product management, which I'm not part of.
Nova-Docker, stable branch has been checked out for driver build,
doesn't
seem to support FIPs ( just pinging works) been installed on RDO Mitaka ( build 20160322
)
Compute Node.
I>'m also clueless about Magnum, so I'll defer answering that to the
magnum maintainers in RDO:
$ rdopkg info openstack-magnum
Per https://wiki.openstack.org/wiki/Magnum
Magnum uses Heat to orchestrate an OS image which contains Docker and Kubernetes and runs
that image in either virtual machines or bare metal in a cluster configuration. Click
below for a 5 minute demo of how Magnum works.
...
maintainers:
- chkumar(a)redhat.com
- mathieu.velten(a)cern.ch
Cheers,
Alan
_______________________________________________
Rdo-list mailing list
Rdo-list(a)redhat.com
https://www.redhat.com/mailman/listinfo/rdo-list
To unsubscribe: rdo-list-unsubscribe(a)redhat.com
_______________________________________________
Rdo-list mailing list
Rdo-list(a)redhat.com
https://www.redhat.com/mailman/listinfo/rdo-list
To unsubscribe: rdo-list-unsubscribe(a)redhat.com
5:26 a.m.
New subject: [Rdo-list] What magnum status in RDO Mitaka is supposed to be ?
Hello,
On Mon, Mar 28, 2016 at 2:21 AM, Boris Derzhavets
<bderzhavets(a)hotmail.com> wrote:
________________________________________
From: rdo-list-bounces(a)redhat.com <rdo-list-bounces(a)redhat.com> on behalf of Boris
Derzhavets <bderzhavets(a)hotmail.com>
Sent: Sunday, March 27, 2016 12:17 PM
To: chkumar(a)redhat.com; rdo-list
Subject: Re: [Rdo-list] What magnum status in RDO Mitaka is supposed to be ?
I attempted manual magnum set up in general updating git checkouts from
Magnum in RDO OpenStack – Liberty Manual Installation from source code :-
http://egonzalez.org/magnum-in-rdo-openstack-liberty-manual-installation-...
I was able start services after rebuild
openstack-magnum-2.0.1-0.20160324110644.c0c2bdb.el7.centos.src.rpm,
which passed CI with build 20160324
Finally I was hit by known bug
http://osdir.com/ml/openstack-dev/2016-02/msg02123.html.
It is possible to run suggested scripts, but I guess keystone v3 is required to get
things done on RDO Mitaka.
In meantime :-
[root@ip-192-169-142-127 ~(keystone_admin)]# nova-manage version
13.0.0-0.20160324111850.803171f.el7.centos
[root@ip-192-169-142-127 ~(keystone_admin)]# keystone endpoint-list | grep 5000
| 43e01cdd87934c4faa7c016fa29c0c69 | RegionOne |
http://192.169.142.127:5000/v2.0 | http://192.169.142.127:5000/v2.0
| http://192.169.142.127:35357/v2.0 | 70d1e7ad70544601a288e42b2f29181a
|
[root@ip-192-169-142-127 ~(keystone_admin)]# rpm -qa \*keystone\*
python-keystoneclient-2.3.2-0.20160318012243.92741ad.el7.centos.noarch
python-keystonemiddleware-4.3.1-0.20160324202909.a0a1e4f.el7.centos.noarch
openstack-keystone-9.0.0.0-0.20160325103215.aa53ad9.el7.centos.noarch
python2-keystoneauth1-2.3.1-0.20160324204310.63267fa.el7.centos.noarch
python-keystone-9.0.0.0-0.20160325103215.aa53ad9.el7.centos.noarch
I guess still RDO Mitaka stays with keystone v2.0 upstream version of magnum for Mitaka
won't be available.
Keystone v3 is available in openstack-keystone package.
You can grab the latest package from delorean repo.
http://trunk.rdoproject.org/centos7/delorean-deps.repo
>My last question is :-
>as far as
http://egonzalez.org/magnum-in-rdo-openstack-liberty-manual-installation-...
>works why packaging is not done for RDO Liberty
This package is introduced in RDO mitaka cycle but a spec file for
RDO magnum liberty is available at
https://github.com/MatMaul/openstack-magnum-spec/tree/mitaka-on-liberty
There is also an Magnum Installation guide :
https://review.openstack.org/#/c/289994/ Feel free to try it and have
your comments there.
Thanks,
Chandan Kumar
9:50 a.m.
Hi,
Why I can't find a similar url for f23 ?
http://trunk.rdoproject.org/f23-mitaka
BTW, usually the f23 trunk can work,
but I still not able to make barbican and cloudkitty
to look like working.
Do they works on centos7 ?
BTW, most of the new components are not registered in Bugzilla,
is it planned to be fixed ?
Best regards,
Attila
----- Original Message -----
From: "David Moreau Simard" <dms(a)redhat.com>
To: "rdo-list" <rdo-list(a)redhat.com>
Sent: Wednesday, March 23, 2016 7:46:06 PM
Subject: [Rdo-list] Reminder: The Mitaka trunk repositories have been
"branched" in preparation for stable release
Hi,
This is just a reminder that, as the release of Mitaka draws near and
the stable/mitaka branches have started appearing upstream, we have
also "branched" Mitaka.
http://trunk.rdoproject.org/centos7 (or
http://trunk.rdoproject.org/centos7-master) has been Newton for around
two weeks now and is entirely untested by the RDO CI at this time.
If you were previously installing from repositories like:
- http://trunk.rdoproject.org/centos7/delorean-deps.repo
- http://trunk.rdoproject.org/centos7/current-passed-ci/delorean.repo
Please transition to:
- http://trunk.rdoproject.org/centos7-mitaka/delorean-deps.repo
- http://trunk.rdoproject.org/centos7-mitaka/delorean.repo.
Since Newton is still untested, things are bound to break and stop working.
As such, please use the Mitaka if you'd like to test the upcoming
release of OpenStack.
Please note that the rdo-release repository RPM is still based on
Liberty as Mitaka has not yet been released upstream.
The anticipated _upstream_ release date for Mitaka is on April 7th [1].
As usual, all of our efforts are currently aimed at doing the general
availability of the RDO stable release of Mitaka as soon as possible.
Our target is to release within 1 week of the upstream stable announcement.
Let us know if you have any questions !
[1]: http://releases.openstack.org/mitaka/index.html
David Moreau Simard
Senior Software Engineer | Openstack RDO
dmsimard = [irc, github, twitter]
_______________________________________________
Rdo-list mailing list
Rdo-list(a)redhat.com
https://www.redhat.com/mailman/listinfo/rdo-list
To unsubscribe: rdo-list-unsubscribe(a)redhat.com
11:07 a.m.
________________________________________
From: rdo-list-bounces(a)redhat.com <rdo-list-bounces(a)redhat.com> on behalf of Attila
Fazekas <afazekas(a)redhat.com>
Sent: Tuesday, March 29, 2016 10:50 AM
To: David Moreau Simard
Cc: rdo-list
Subject: Re: [Rdo-list] Reminder: The Mitaka trunk repositories have been
"branched" in preparation for stable release
Hi,
Why I can't find a similar url for f23 ?
http://trunk.rdoproject.org/f23-mitaka
Please, see
1. https://www.redhat.com/archives/rdo-list/2016-March/msg00092.html
2. https://www.redhat.com/archives/rdo-list/2016-March/msg00117.html
Thank you for your warning message regarding Magnum Set up on Mitaka.
Boris.
BTW, usually the f23 trunk can work,
but I still not able to
make barbican and cloudkitty
to look like working.
Do they works on centos7 ?
BTW, most of the new components are not registered in Bugzilla,
is it planned to be fixed ?
Best regards,
Attila
----- Original Message -----
From: "David Moreau Simard" <dms(a)redhat.com>
To: "rdo-list" <rdo-list(a)redhat.com>
Sent: Wednesday, March 23, 2016 7:46:06 PM
Subject: [Rdo-list] Reminder: The Mitaka trunk repositories have been
"branched" in preparation for stable release
Hi,
This is just a reminder that, as the release of Mitaka draws near and
the stable/mitaka branches have started appearing upstream, we have
also "branched" Mitaka.
http://trunk.rdoproject.org/centos7 (or
http://trunk.rdoproject.org/centos7-master) has been Newton for around
two weeks now and is entirely untested by the RDO CI at this time.
If you were previously installing from repositories like:
- http://trunk.rdoproject.org/centos7/delorean-deps.repo
- http://trunk.rdoproject.org/centos7/current-passed-ci/delorean.repo
Please transition to:
- http://trunk.rdoproject.org/centos7-mitaka/delorean-deps.repo
- http://trunk.rdoproject.org/centos7-mitaka/delorean.repo.
Since Newton is still untested, things are bound to break and stop working.
As such, please use the Mitaka if you'd like to test the upcoming
release of OpenStack.
Please note that the rdo-release repository RPM is still based on
Liberty as Mitaka has not yet been released upstream.
The anticipated _upstream_ release date for Mitaka is on April 7th [1].
As usual, all of our efforts are currently aimed at doing the general
availability of the RDO stable release of Mitaka as soon as possible.
Our target is to release within 1 week of the upstream stable announcement.
Let us know if you have any questions !
[1]: http://releases.openstack.org/mitaka/index.html
David Moreau Simard
Senior Software Engineer | Openstack RDO
dmsimard = [irc, github, twitter]
_______________________________________________
Rdo-list mailing list
Rdo-list(a)redhat.com
https://www.redhat.com/mailman/listinfo/rdo-list
To unsubscribe: rdo-list-unsubscribe(a)redhat.com
_______________________________________________
Rdo-list mailing list
Rdo-list(a)redhat.com
https://www.redhat.com/mailman/listinfo/rdo-list
To unsubscribe: rdo-list-unsubscribe(a)redhat.com
3159
days inactive
3165
days old
10 comments
5 participants
participants (5)
-
Alan Pevec -
Attila Fazekas -
Boris Derzhavets -
Chandan kumar -
David Moreau Simard