cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <>
Subject [jira] [Commented] (CLOUDSTACK-10024) Physical Networking Migration
Date Wed, 20 Dec 2017 08:55:00 GMT


ASF GitHub Bot commented on CLOUDSTACK-10024:

krissterckx commented on issue #2259: CLOUDSTACK-10024: Network migration support
   @borisstoyanov this PR adds MigrateNetworkCmd.class and MigrateVPCCmd.class as new commands,
which just causes git not to know in which order to add them.
   The problem is, we can keep on rebasing - each time some other commits goes in, we possibly
need to rebase again :-)  We can/will do that but i also would like to see review and Trillian
results. Do you prefer us to rebase again first ?

This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:

> Physical Networking Migration
> -----------------------------
>                 Key: CLOUDSTACK-10024
>                 URL:
>             Project: CloudStack
>          Issue Type: New Feature
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: API, KVM, Management Server, VMware
>            Reporter: Frank Maximus
>            Assignee: Frank Maximus
>             Fix For:
> *As a* Cloud Owner
> *I want to* migrate my existing guest networks to another physical network infrastructure
> *In order to* leverage new network technologies, e.g. leverage SDN.

This message was sent by Atlassian JIRA

View raw message