Hi Nirmal, STRATOS-507 which I'm planning to submit this week is about attaching to a cartridge fixed private Ips for their respective private network UUIDs. If you can recall you did some enhancement in STRATOS-180 to allow attaching network UUIDs to a cartridge. STRATOS-507 takes it one step further to allow attaching an IP and possibly port UUID for the respective network UUID. Without STRATOS-507, the new instance will get a random private IP for each of the network.
On the other hand, STRATOS-493 deals with the assignment of a fixed floating IP instead of getting a random one from the floating IP pool. It's similar to STRATOS-507 but it's a different concept and the code is different too. HTH, -Jeffrey On 3/17/14 8:39 PM, "Nirmal Fernando (JIRA)" <[email protected]> wrote: > > [ >https://issues.apache.org/jira/browse/STRATOS-493?page=com.atlassian.jira. >plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13938753#co >mment-13938753 ] > >Nirmal Fernando commented on STRATOS-493: >----------------------------------------- > >Hi Martin, > >Is this fix conflicts with >https://issues.apache.org/jira/browse/STRATOS-507 fix? > >PS: I've assigned the issue to you now. > >> Assign a predefined floating ip >> -------------------------------- >> >> Key: STRATOS-493 >> URL: https://issues.apache.org/jira/browse/STRATOS-493 >> Project: Stratos >> Issue Type: Improvement >> Components: Cloud Controller >> Affects Versions: 4.0.0 Alpha >> Reporter: Martin Eppel >> Assignee: Martin Eppel >> Labels: patch >> Fix For: FUTURE >> >> Attachments: >>0001-support-for-predefined-floating-ip-jira-STRATOS-493.patch >> >> Original Estimate: 168h >> Remaining Estimate: 168h >> >> Instead of auto assigning the floating ip address from the pool >>(autoAssignIp ³false² in cartridgeDefinitionBean:iaasProvider, see >>example below), the ip address would be predefined in the cartridge >>definition as an additional property (see example below with property >>³floatingIp², ) and if available in the floating ip pool, assigned to >>the instance when it is created. If the floating ip is unavailable, an >>exception will be thrown and the instance will be destroyed. >> >> As for now it would be sufficient to add this enhancement for the >>OpenStack provider. >> Configuration Example: >> Š >> "iaasProvider": >> [ >> { >> "type": "openstack", >> "imageId": "RegionOne/${IMAGE_ID}", >> "maxInstanceLimit": "4", >> "property": >> [ >> { >> "name": "instanceType", >> "value": "RegionOne/${FLAVOR_ID}" >> }, >> { >> "name": "keyPair", >> "value": "${KEY}" >> }, >> { >> "name": "autoAssignIp", >> "value": "false² >> }, >> { >> "name": "floatingIp", >> "value": "10.10.10.10² >> }, >> { >> "name": "securityGroups", >> "value": "default" >> }, >> { >> "name": "networkInterfaces", >> "value": ³net1,net2,net3² >> } >> ] >> } >> ], >> Š > > > >-- >This message was sent by Atlassian JIRA >(v6.2#6252)
