Thanks Steve. That was in fact meant to say “RPMs aren’t present in RDO”. Sorry for the confusion.
I did end up installing the python-magnumclient via pip for now, but we strongly prefer to do installation via RPM instead. I’d love to see Magnum and related packages included in RDO. Meanwhile I’m still plugging away at trying to get Magnum working correctly and am making fairly decent progress. I’m sure I’ll have some additional questions for the group soon. Thanks, Mike On Aug 19, 2015, at 2:48 PM, Steve Gordon <sgor...@redhat.com<mailto:sgor...@redhat.com>> wrote: ----- Original Message ----- From: "David Medberry" <openst...@medberry.net<mailto:openst...@medberry.net>> To: "Mike Smith" <mism...@overstock.com<mailto:mism...@overstock.com>> Distributions are respectively responsible for what they package or don't package (though if they package the service they SHOULD IMHO package a functioning client.) There is an overall project (or two) to get to a single common client. RDO doesn't currently package magnum (service or client), I believe the sentence "Since the Magnum RPMs are present in RDO, I’m using RPMs built by one of the Magnum developers (available at https://copr-be.cloud.fedoraproject.org/results/sdake/openstack-magnum/)" in the original email was meant to say *aren't*. Steve doesn't have an equivalent COPR for python-magnumclient, I believe because the expectation at the moment is that you would just pull it from pip. I did kick off a thread on the RDO community mailing list about how to handle "packaging the big tent" in RDO a while ago as we expect demand for more projects to be included to increase in the future but we didn't reach a clear resolution yet: https://www.redhat.com/archives/rdo-list/2015-May/thread.html#00284 I need to pick this up again but the idea is ideally to make it easier for interested RDO community members to package OpenStack projects they are interested in and get them included in the distribution. Thanks, Steve On Tue, Aug 18, 2015 at 2:09 PM, Mike Smith <mism...@overstock.com<mailto:mism...@overstock.com>> wrote: Thanks. I’ll check it out. Can anyone out there tell me how projects like python-magnumclient and the openstack-magnum software itself get picked up by the RDO folks? I’d like to see those be picked up in their distro but I’m not sure where that work takes place. Do project developers typically package up their projects and make them available to the RDO maintainers or do RedHat folks pick up sources from the projects, do the packaging, and make those packages available? We can start building our own packages for this of course, but as operators prefer not to because of all the dependency overhead. Unless it’s something we can do to help get the packages into the RDO repos (i.e. become a package maintainer as a way of contributing) Mike Smith Principal Engineer / Cloud Team Lead Overstock.com<http://Overstock.com> On Aug 18, 2015, at 2:47 PM, David Medberry <openst...@medberry.net> wrote: http://git.openstack.org/cgit/openstack/python-magnumclient On Tue, Aug 18, 2015 at 12:21 PM, Mike Smith <mism...@overstock.com> wrote: I’m trying to use Magnum on our Openstack Kilo cloud which runs CentOS 7 and RDO. Since the Magnum RPMs are present in RDO, I’m using RPMs built by one of the Magnum developers (available at https://copr-be.cloud.fedoraproject.org/results/sdake/openstack-magnum/) Once I got rid of a conflicting UID that it tries to use for the magnum user, I’m able to start up the services. However, following along with the Magnum documentation that exists ( http://docs.openstack.org/developer/magnum/), the next step is to use the “magnum” command to define things like bay models and bays. However, the “magnum” command doesn’t seem to exist. I’m not sure if it’s supposed to exist as a symlink to something else? Is anyone else out there using Magnum with RDO Kilo? I’d love to chat with someone else that has worked through these issues. Thanks, Mike Mike Smith Principal Engineer / Cloud Team Lead Overstock.com <http://overstock.com/> _______________________________________________ OpenStack-operators mailing list OpenStack-operators@lists.openstack.org<mailto:OpenStack-operators@lists.openstack.org> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators _______________________________________________ OpenStack-operators mailing list OpenStack-operators@lists.openstack.org<mailto:OpenStack-operators@lists.openstack.org> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators -- Steve Gordon, RHCE Sr. Technical Product Manager, Red Hat Enterprise Linux OpenStack Platform
_______________________________________________ OpenStack-operators mailing list OpenStack-operators@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
