Hi Jeremy,
> Can you comment more on what needs to be updated in Sahara? Are they
> simply issues in the UI (sahara-dashboard) or is there a problem
> consuming community images on the server side?
We haven't looked into it much yet, so I couldn't tell you.
I think it would be great to extend
Hi all,
We've recently moved to using Glance's community visibility on the Nectar
Research Cloud. We had lots of public images (12255), and we found it was
becoming slow to list them all and the community image visibility seems to
fit our use-case nicely.
We moved all of our user's images over
Hi Ritesh,
I also found it difficult to build Trove images. We had some infrastructure
already set up for building other images, so we used that for our Trove
images, rather than the OpenStack disk image builder.
We decided to use Ubuntu Xenial (although not supported in Trove at the
time) with
We caught up with some of the Catalyst guys at the Melbourne OpenStack
Australia day and they gave us a demo of this. Looks like a really nice
project that I think might replace some of existing user management
workflow.
Allowing project managers to invite collaborators and self-manage their
We caught up with some of the Catalyst guys at the Melbourne OpenStack
Australia day and they gave us a demo of this. Looks like a really nice
project that I think might replace some of existing user management
workflow.
Allowing project managers to invite collaborators and self-manage their
;
>> Yup, that healthcheck middleware was made more advanced by me,
>>
>> If u need to do anything special with it, let me know and I can help
>> make that possible (or at least instruct what might need changed to do
>> that).
>>
>> Simon Pasquier wrote
Hi Simon,
> There's a healthcheck oslo.middleware plugin [1] available. So you could
> possibly configure the service pipeline to include this except it won't
> exercise the db connection, RabbitMQ connection, and so on. But it would
> help if you want to kick out a service instance from the
We're running our services clustered behind an F5 loadbalancer in
production, and haproxy in our testing environment. This setup works quite
well for us, but I'm not that happy with testing the health of our
endpoints.
We're currently calling basic URLs like / or /v2 etc and some services
return
Hi Emilien,
> I looked again at your module and I see two options:
>
> * import your module in OpenStack and make it compliant (your module
> does not have tests, readme, and some pieces are missing), and cleanup a
> lot of things
>
Just want to confirm you're looking at this new repo:
Hi Emillien,
> I think we would love having this module part of OpenStack, if it's ok
> for you.
>
> The process to move it is documented [1] but I can take care of it if
> you prefer, just let me know.
>
> Thanks for your collaboration, we're looking forward to have
> puppet-rally part of our
Hi Emilien,
> Emilien Macchi wrote:
> > I just noticed we have a second module written by Cody:
> > https://github.com/ody/puppet-rally
> >
> > We might want to collaborate on that.
> >
>
> Yeah...I'd actually completely forgotten that existed until Emilien
> mentioned it to me in IRC.
>
> It
11 matches
Mail list logo
