>> And I want to say folks, I feel your pain. I come from a QA and
>> operations background in large, mission critical, distributed systems
>> and logs have always been my best friends **and** the bane of my
>> existence when they don’t have what you need. I get it. I want to help
>> fix it.
>
> Hi operators,
>
> I wanted to ask for feedback on a design issue regarding DHCP agent and IP per
> agent.
Very happy about dev's coming here for input :)
> Now, regarding the IP consumption there are two possible alternatives:
> 1. Use single IP per serviced subnet for all the servers. (simila
On 2014-10-07 07:40:55 + (+), Robert van Leeuwen wrote:
[...]
> We recently setup logstash here and doing the grok magic was quite
> a pain with all the different way's the logging is formatted. We
> also throw a bit in the bin because there is no useful info in it.
>
> Looking at our logs
Single IP per DHCP is nice.
And move dhcp agent away from network node gives important thing: you
can create isolated tenant networks without headache with dhcp-agents
scheduling. Neutron does not supports now AZ from nova, and DHCP is just
yet another thing to mess up with isolation.
Some i
As far as I know, it is not possible to assign uuid from deleted image
to the new one, because deleted images keeps their metadata in DB.
On 09/26/2014 04:43 PM, Abel Lopez wrote:
Glance images are immutable. In order to update it, you should do as
you are doing, but then rename the old image,
You are correct, deleted images are not deleted from the DB, rather their row
has ‘deleted=1’, so specifying the UUID of another image already in glance for
a new image being upload will end in tears.
What I was trying to convey was, when Christian is uploading a new image of the
same name as a
Hello,
I use Your solution and I made old images as private in such change but then
there is one more problem: all instances spawned from that old images are have
in horizon info about image: "not found".
Do You maybe know how to solve that?
---
Best regards
Sławek Kapłoński
[email protected]
I've never worried about "Image not Found", as its only a UI concern. IMO
it lets the users know something has changed. Totally optional, and the
same effect can be gained by just renaming it -OLD and leaving it public.
At some point, it still needs to be removed.
On Tuesday, October 7, 2014, Sław
It would be nice to have an archive status for images, where brand new
instances may not be launched off it, but where it may be used as a
reference for existing instances and snapshots.
Not sure about other folks, but we just keep piling up the old images, and
they have to remain public. There's
Hello,
Yes, I agree that this is not big problem when there is info "Image not found"
in horizon but I saw this discussion and I thought that I will ask about that
:) It would be nice to have some other info like for example: "Image 1
(archived)" or something like that :)
---
Best regards
Sław
Right, and I think the best thing about marking a deprecated image private is
that
new instances can’t select that image unless the tenant is an image-member of
it.
So if a specific tenant has some “real valid” need to use the old version (I
can’t imagine why), they could find it in “Project Ima
Hi,
Please note the issue reported in
https://bugs.launchpad.net/nova/+bug/1160773: "Cannot resize instance if
base image is not available"
AFAIK it is still the case that instances cannot be resized or migrated
once the image from which it has been created has been deleted.
cheers, Jan
O
Yep, this bug is still actual. Resize, migration and so on does not work
if original image is deleted. And 'I will never remove any public image'
will not helps, because if user restore instance from snapshot and
remove snapshot it will cause error too. That looks stupid in the light
of (our) r
Il 07/10/2014 16:31, Jeremy Stanley ha scritto:
> Indeed, OpenStack's project infrastructure and quality assurance
> teams have been collaboratively managing a very large
> logstash+elasticsearch cluster for use in classifying bugs witnessed
> while performing CI testing on proposed changes. The in
14 matches
Mail list logo
