| 2013-06-03 06:07:30 |
Sergey Lukjanov |
bug |
|
|
added bug |
| 2013-06-03 06:25:55 |
Sergey Lukjanov |
savanna: status |
New |
Triaged |
|
| 2013-06-03 06:25:57 |
Sergey Lukjanov |
savanna: importance |
Undecided |
High |
|
| 2013-06-03 06:25:59 |
Sergey Lukjanov |
savanna: assignee |
|
Sergey Lukjanov (slukjanov) |
|
| 2013-06-03 06:26:01 |
Sergey Lukjanov |
savanna: milestone |
|
0.2a1 |
|
| 2013-06-03 06:26:06 |
Sergey Lukjanov |
tags |
|
0.2 |
|
| 2013-06-05 08:25:45 |
Sergey Lukjanov |
summary |
Implement management ip selection policy mechanism |
Implement ip selection policy mechanism |
|
| 2013-06-05 08:25:53 |
Sergey Lukjanov |
description |
We should implement some management ip selection policy mechanism that will allow Savanna to identify correct management ip address.
For example:
* specifying nova network name [and ip # in it]
* specifying network - X.X.X.X/XX
* autodiscovery (Savanna will try all ips os the instance) |
We should implement some ip selection policy mechanism that will allow Savanna to identify correct management ip address.
For example:
* specifying nova network name [and ip # in it]
* specifying network - X.X.X.X/XX
* autodiscovery (Savanna will try all ips os the instance) |
|
| 2013-06-05 08:29:39 |
Sergey Lukjanov |
description |
We should implement some ip selection policy mechanism that will allow Savanna to identify correct management ip address.
For example:
* specifying nova network name [and ip # in it]
* specifying network - X.X.X.X/XX
* autodiscovery (Savanna will try all ips os the instance) |
We should implement some ip selection policy mechanism that will allow Savanna to identify correct management ip address.
For example:
* specifying nova network name [and ip # in it]
* specifying network - X.X.X.X/XX
* autodiscovery (Savanna will try all ips os the instance, btw, I think it's very bad to do it) |
|
| 2013-06-24 12:19:53 |
Sergey Lukjanov |
savanna: milestone |
0.2a1 |
0.2 |
|
| 2013-07-04 09:35:04 |
Sergey Lukjanov |
tags |
0.2 |
0.3 |
|
| 2013-07-04 09:35:07 |
Sergey Lukjanov |
savanna: milestone |
0.2 |
0.3 |
|
| 2013-08-21 15:01:56 |
ruhe |
savanna: milestone |
0.3 |
|
|
| 2013-08-21 15:02:06 |
ruhe |
savanna: importance |
High |
Medium |
|
| 2013-08-21 15:02:10 |
ruhe |
savanna: importance |
Medium |
Low |
|
| 2013-09-06 13:48:28 |
Nikita Konovalov |
savanna: assignee |
Sergey Lukjanov (slukjanov) |
Nikita Konovalov (nkonovalov) |
|
| 2013-09-06 13:56:18 |
Nikita Konovalov |
description |
We should implement some ip selection policy mechanism that will allow Savanna to identify correct management ip address.
For example:
* specifying nova network name [and ip # in it]
* specifying network - X.X.X.X/XX
* autodiscovery (Savanna will try all ips os the instance, btw, I think it's very bad to do it) |
We should implement some ip selection policy mechanism that will allow Savanna to identify correct management ip address.
After an instance is created, it will have an internal ip:
* automatically for Nova Network
* defined by user for Neutron
User may specify an Floaing IP Pool name for any Node Group in a Node Group Template, so that instances in specified Node Group will have Floating IPs assigned.
If 'use_floating_ips' option in config is set to True, Savanna will use floating IP of an Instance for management operations. Aslo a validation should be provided not to let user create a Cluster in which there are Node Groups without Floating IP Pool name. |
|
| 2013-09-06 13:56:30 |
Nikita Konovalov |
description |
We should implement some ip selection policy mechanism that will allow Savanna to identify correct management ip address.
After an instance is created, it will have an internal ip:
* automatically for Nova Network
* defined by user for Neutron
User may specify an Floaing IP Pool name for any Node Group in a Node Group Template, so that instances in specified Node Group will have Floating IPs assigned.
If 'use_floating_ips' option in config is set to True, Savanna will use floating IP of an Instance for management operations. Aslo a validation should be provided not to let user create a Cluster in which there are Node Groups without Floating IP Pool name. |
We should implement some ip selection policy mechanism that will allow Savanna to identify correct management ip address.
After an instance is created, it will have an internal ip:
* automatically for Nova Network
* defined by user for Neutron
User may specify an Floating IP Pool name for any Node Group in a Node Group Template, so that instances in specified Node Group will have Floating IPs assigned.
If 'use_floating_ips' option in config is set to True, Savanna will use floating IP of an Instance for management operations. Aslo a validation should be provided not to let user create a Cluster in which there are Node Groups without Floating IP Pool name. |
|
| 2013-09-06 13:56:47 |
Nikita Konovalov |
savanna: status |
Triaged |
Fix Committed |
|
| 2013-09-06 13:56:53 |
Nikita Konovalov |
savanna: status |
Fix Committed |
In Progress |
|
| 2013-09-06 14:10:07 |
ruhe |
savanna: milestone |
|
0.3a1 |
|
| 2013-09-06 14:18:53 |
ruhe |
tags |
0.3 |
0.2.2 0.3 |
|
| 2013-09-09 10:29:03 |
Andrew Lazarev |
bug |
|
|
added subscriber Andrew Lazarev |
| 2013-09-16 15:04:36 |
Sergey Lukjanov |
tags |
0.2.2 0.3 |
0.3 |
|
| 2013-09-16 15:04:46 |
Sergey Lukjanov |
savanna: importance |
Low |
High |
|
| 2013-09-24 04:05:49 |
OpenStack Infra |
savanna: status |
In Progress |
Fix Committed |
|
| 2013-09-30 15:41:50 |
Sergey Lukjanov |
savanna: status |
Fix Committed |
Fix Released |
|
| 2013-10-17 19:39:17 |
Sergey Lukjanov |
savanna: milestone |
0.3a1 |
0.3 |
|
