Hi Matthew, I don't know how others feel about this, but I don't think that the core CloudStack code is the place for Proof-of-Concepts.
I have nothing against your VyOS concept, in fact I have suggested it as an alternative in the past and I kicked off a Blue Orangutan build and looked at what you had done so far. My personal feeling is that the we (you) need to have a branch which is kept in sync with master that is used for this work. My 2p worth, is that the part that really needs PoC is refactoring the code such that the VyOS can be deployed in place of a VR, then that CloudStack can send commands to alternate 'drivers' when configuring what it sees as a user created VR. I really don't wish to **** on your bonfire, I think that this is a great project I would love to help out with it... Kind regards, Paul Angus paul.an...@shapeblue.com www.shapeblue.com 53 Chandos Place, Covent Garden, London WC2N 4HSUK @shapeblue -----Original Message----- From: Matthew Smart [mailto:msm...@smartsoftwareinc.com] Sent: 03 June 2017 12:50 To: dev@cloudstack.apache.org Subject: Re: [apache/cloudstack] Vyos router plugin (#2105) This didn't go through the first time for some reason... Hey guys, I know this is going to take some time to merge. In the meantime, I am preparing my design for the next iteration of the plugin which will tentatively add DNS, DHCP, VPN, and maybe VRRP (redundant routing) support. I am not very familiar with GIT or the PR process. Assuming my design phase completes before my PR is merged how should I go about starting work on the next iteration of the plugin? Can I create a new branch from the branch that is waiting for the PR to be merged and make my changes there? Thanks, Matthew Smart President Smart Software Solutions Inc. 108 S Pierre St. Pierre, SD 57501 Phone: (605) 280-0383 Skype: msmart13 Email: msm...@smartsoftwareinc.com -------- Forwarded Message -------- Subject: Re: [apache/cloudstack] Vyos router plugin (#2105) Date: Fri, 2 Jun 2017 15:47:37 -0500 From: Matthew Smart <msm...@smartsoftwareinc.com> To: reply+0133cbd45f36984313fd3e0860108796fac2fb386eb2d6d492cf00000001153d1d reply+b792a169ce0da2c...@reply.github.com Hey guys, I know this is going to take some time to merge. In the meantime, I am preparing my design for the next iteration of the plugin which will tentatively add DNS, DHCP, VPN, and maybe VRRP (redundant routing) support. I am not very familiar with GIT or the PR process. Assuming my design phase completes before my PR is merged how should I go about starting work on the next iteration of the plugin? Can I create a new branch from the branch that is waiting for the PR to be merged and make my changes there? Thanks, Matthew Smart President Smart Software Solutions Inc. 108 S Pierre St. Pierre, SD 57501 Phone: (605) 280-0383 Skype: msmart13 Email:msm...@smartsoftwareinc.com On 05/24/2017 05:08 AM, Blue Orangutan Build Things wrote: > > Packaging result: ✔centos6 ✔centos7 ✔debian. JID-741 > > — > You are receiving this because you were mentioned. > Reply to this email directly, view it on GitHub > <https://github.com/apache/cloudstack/pull/2105#issuecomment-303679093 > >, > or mute the thread > <https://github.com/notifications/unsubscribe-auth/ATPL1JdWfN4FiJb3qjC > 15mP-6zmdwUneks5r9AG3gaJpZM4NbYdv>.Web > Bug from > https://github.com/notifications/beacon/ATPL1CU8Qdww8m5wKxzpzxmhtOcv9O > KMks5r9AG3gaJpZM4NbYdv.gif >
