Re: [Openstack-operators] ocata boot source launch missing options
Emilio, There is a bug in Horizon - https://bugs.launchpad.net/horizon/+bug/1670789 Briefly: in the case where there is no cinder v1 endpoint created certain volume related menu entries are not displayed. This issue was fixed in the 11.0.3. How do you deploy? You may upgrade your environment or just create some endpoints in the catalog Thanks > On 30 Jun 2017, at 10:13, Emilio Moreno Fernandez <emilio.mor...@adam.es> > wrote: > > Hi! > > We have a very strange error in our new platform Ocata that in previous > Liberty or Juno had not happened to me. > When you want to launch an instance from the Dashboard, in boot options only > the option "Image" or "Instance Snapshot" appears ... I do not get the volume > options appear. > > Cinder and Glance work correctly, Image to Volume or Volume to Image, create > image, create volume, etc ... > > Any ideas? > > Emilio Moreno Fernández > ___ > OpenStack-operators mailing list > OpenStack-operators@lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators -- Best Regards, Evgeniy Ivanov. Sardina Systems +442034114590 ___ OpenStack-operators mailing list OpenStack-operators@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
[Openstack] Trove clustering
Hello, What datastores officially supported for Trove clustering? (apart of mongodb). According to the Trove/DatastoreCompatibilityMatrix there are no any other datastores with stable clustering. Is that correct? Thanks! -- Best Regards, Evgeniy Ivanov ___ Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack Post to : openstack@lists.openstack.org Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
[Openstack-operators] Networking in Trove. Security question
Hello, I use Trove on my test environment and some things look very insecurely for me. The base trove schema requires access to the MQ service from guest instances, that means the network allocated to guest instances (let's call it the trove network) should has access to the management network (where the MQ servers placed), but in order to allocate a network port on the trove network a client need to have access to this network. The question is — what does prevent (or can prevent) users to create an instance (not a trove guest, but just a common compute instance) in the same trove network and get access to the management network (at least to the MQ service). It’s not a problem for trove guests, because clients don’t have SSH access to trove guests. Seems, nothing does and any clients can just allocate instances on the trove network and get access to the MQ service (next, ddos is a possible security violation at least) I found the config option trove_managed_net_id in the Trove wiki, but there are no mentions how to use it and I can not find any terminations of those options in the trove code (newton release) Thanks. -- Best Regards, Evgeniy Ivanov ___ OpenStack-operators mailing list OpenStack-operators@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
Re: [Openstack] Trove is skipped in Newton
Amrith Kumar, Thanks for your reply. > [Amrith Kumar] I don't quite understand where Tesora got involved in this Tesora as a contributor did more then 60% for Trove, didn't they? So, if you as a major contributor of Trove and you don't want to write documentations, why don't you opensource the book? (Openstack Trove) and make life easer for operators ? According to the information I found on the openstack repositories I can tell exactly that it's absolutely impossible to build an image and get trove-guestagent up and running in Newton for now. That's why I made the thread and asked for help. On 07/03/17 17:09, Amrith Kumar wrote: -Original Message- From: Evgeniy Ivanov [mailto:e601...@gmail.com] Sent: Monday, March 6, 2017 11:13 PM To: openstack@lists.openstack.org Subject: [Openstack] Trove is skipped in Newton Hello everybody, I found some interesting info about Trove in Newton. I'm able to deploy successfully some trove components (api, conductor and taskmanager) on my test Newton environment. As for the Trove guestagent - I'm totally not able to run it neither on Ubuntu Trusty nor Ubuntu Xenial. I found there are no Newton packages for Trusty in The Ubuntu Cloud Archive. The last supported release is Mitaka (I checked the RELEASE_MAP). That looks there is no support for Newton in Trusty, therefore I can not use Trove in Newton. [Amrith Kumar] This appears to be more of a question for the Ubuntu distribution maintainers than for the Trove project. As for the Xenial release, here is a bug where Amrith Kumar (CTO Tesora) says there is no support for Newton also - https://bugs.launchpad.net/trove/+bug/1652312 (Should be in Ocata only) [Amrith Kumar] This was specific to the MySQL support and as the comment in the bug says, "fwiw, xenial support for mysql does exist in master (soon Ocata)." For me, it looks like Tesora just skipped Newton, did they? [Amrith Kumar] No, but you should distinguish between Tesora and Trove. FYI, my response is only as a contributor to Trove, I do not speak for Tesora. As with next comment, I don't see what Tesora has to do with this if you aren't using their software. I'm asking here because there is no way to get any answers from Tesora and Co. [Amrith Kumar] I don't quite understand where Tesora got involved in this but I'll assume that you are their customer and you know how to get support. If not, then I don't see what you'd like them to do for you. If you are attempting to use packages from the Ubuntu Cloud Archive (as you say you are), it doesn't strike me that you are a Tesora customer. Thanks for any help! -- Best Regards, Evgeniy Ivanov ___ Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack Post to : openstack@lists.openstack.org Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack -- Best Regards, Evgeniy Ivanov ___ Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack Post to : openstack@lists.openstack.org Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
[Openstack] Trove is skipped in Newton
Hello everybody, I found some interesting info about Trove in Newton. I'm able to deploy successfully some trove components (api, conductor and taskmanager) on my test Newton environment. As for the Trove guestagent - I'm totally not able to run it neither on Ubuntu Trusty nor Ubuntu Xenial. I found there are no Newton packages for Trusty in The Ubuntu Cloud Archive. The last supported release is Mitaka (I checked the RELEASE_MAP). That looks there is no support for Newton in Trusty, therefore I can not use Trove in Newton. As for the Xenial release, here is a bug where Amrith Kumar (CTO Tesora) says there is no support for Newton also - https://bugs.launchpad.net/trove/+bug/1652312 (Should be in Ocata only) For me, it looks like Tesora just skipped Newton, did they? I'm asking here because there is no way to get any answers from Tesora and Co. Thanks for any help! -- Best Regards, Evgeniy Ivanov ___ Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack Post to : openstack@lists.openstack.org Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
[Openstack] Upgrade Mitaka to Newton. Nova 13 does not work with Nova 14
Hello! I'm experiencing some kind of a bug, when I have a controller with mitaka and a controller with Newton. When I upgraded the first part of my cluster to Newton, the second part stopped to work (nova-api). I got this error: oslo_service.service ServiceTooOld: This service is older (v9) than the minimum (v15) version of the rest of the deployment. Unable to continue. So, as we can see, all those dialogs, manuals, docs, posts which are talking about compatibility between 2 releases are wrong, aren't they? I will be happy to read some thoughts from you guys, thanks! How to reproduce: Install nova 13 on 2 nodes Disable the first node Upgrade the first node to nova 14 Restart nova-api on the second node (13 ver.) -- Best Regards, Evgeniy Ivanov ___ Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack Post to : openstack@lists.openstack.org Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Re: [Openstack] Upgrade from Mitaka to Newton. Nova 13 does not worn to work witn Nova 14
Sorry for duplicate, please, ignore this thread On 14/12/16 10:35, Evgeniy Ivanov wrote: Hello! I'm experiencing some kind of a bug, when I have a controller with mitaka and a controller with Newton. When I upgraded the first part of my cluster to Newton, the second part stopped to work (nova-api). I got this error: oslo_service.service ServiceTooOld: This service is older (v9) than the minimum (v15) version of the rest of the deployment. Unable to continue. So, as we can see, all those dialogs, manuals, docs, posts which are talking about compatibility between 2 releases are wrong, aren't they? I will be happy to read some thoughts from you guys, thanks! How to reproduce: Install nova 13 on 2 nodes Disable the first node Upgrade the first node to nova 14 Restart nova-api on the second node (13 ver.) -- Best Regards, Evgeniy Ivanov ___ Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack Post to : openstack@lists.openstack.org Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
[Openstack] Upgrade from Mitaka to Newton. Nova 13 does not worn to work witn Nova 14
Hello! I'm experiencing some kind of a bug, when I have a controller with mitaka and a controller with Newton. When I upgraded the first part of my cluster to Newton, the second part stopped to work (nova-api). I got this error: oslo_service.service ServiceTooOld: This service is older (v9) than the minimum (v15) version of the rest of the deployment. Unable to continue. So, as we can see, all those dialogs, manuals, docs, posts which are talking about compatibility between 2 releases are wrong, aren't they? I will be happy to read some thoughts from you guys, thanks! How to reproduce: Install nova 13 on 2 nodes Disable the first node Upgrade the first node to nova 14 Restart nova-api on the second node (13 ver.) -- Best Regards, Evgeniy Ivanov ___ Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack Post to : openstack@lists.openstack.org Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
