Please hold on testing that involves service VMs

Vasiliy Kochergin

unread,

Dec 9, 2014, 2:50:50 PM12/9/14

to Engineering, Quality Assurance Team, Customer Success Team

Folks,
There is work in progress to change all service VMs (ELB, Imaging
Worker, DB). I see there are some bugs filed about them. All VMs are
about to change. Please don't waste your time testing something that
is about to go way. Please don't file new bugs about service VMs until
you are using right VM.
If you have any questions please first read
https://eucalyptus.atlassian.net/wiki/display/QA/Service+Image+Lifecycle.
If you still have questions after that please contact Dima, Vic or
myself.

Vasya.

Imran Hossain Shaon

unread,

Dec 10, 2014, 4:07:04 AM12/10/14

to Vasiliy Kochergin, Engineering, Quality Assurance Team, Customer Success Team

Thanks for the heads up Vasya.

I totally agree with all the 9 reasons and I like the approach we are taking now. Few questions:

a) Is it going to be a 4.1.0 thing or we are expecting it in the next major release?

b) Why it wouldn't be a good idea to use the same Eucalyptus version name for service-image version? Also, I think, some kind of tagging/versioning should be there for the bash script/user-data, just to make sure that no one is running an outdated version. (eugle-describe-service-images meets that requirement mostly)

c) Do we have a ticket on these changes? An story perhaps? It would be really great for other to keep track of these changes from there and have the confluence link attached.

d) and the most important question, what does eugle mean? :)

Thanks,

Shaon

Vasiliy Kochergin

unread,

Dec 10, 2014, 6:31:57 PM12/10/14

to Imran Hossain Shaon, Engineering, Quality Assurance Team, Customer Success Team

> I totally agree with all the 9 reasons and I like the approach we are taking
> now. Few questions:
>
> a) Is it going to be a 4.1.0 thing or we are expecting it in the next major
> release?

The unified service VM image is part of 4.1

> b) Why it wouldn't be a good idea to use the same Eucalyptus version name
> for service-image version? Also, I think, some kind of tagging/versioning
> should be there for the bash script/user-data, just to make sure that no one
> is running an outdated version. (eugle-describe-service-images meets that
> requirement mostly)

Extensive and well established version formats are currently in
discussion and probably will not be part of 4.1.

> c) Do we have a ticket on these changes? An story perhaps? It would be
> really great for other to keep track of these changes from there and have
> the confluence link attached.

There are several tasks in JIRA
https://eucalyptus.atlassian.net/secure/RapidBoard.jspa?rapidView=98

> d) and the most important question, what does eugle mean? :)

I think this is refers to a command that does not have established
name and output format at the moment.

Vasya

Reply all

Reply to author

Forward