Re: [DISCUSS] SIG for SDN Tungsten Fabric Network Plugin
That's a nice initiative and good timing, we will be interesting and willing to contribute as well, if we go with tungsten Fabric. We recently looked at using Contrail, the commercial version of Tungsten, not very impressed for managing network switches to be honest. Overcomplicated software with limited configuration schema for switches. Although we haven't looked at the service orchestration part. It seems to be somewhat useful when it comes to orchestrate services such as firewall, LB, vxlan routers,... Will also be challenging to deal with their documentation which lacked a bit and also their high integration to OpenStack :-( We are expecting to have a close eye on Tungsten for our network services evolution. Perso, I would look for another SDN, but I'm not knowledgeable in this topic at the moment, it might be the best open source option available at the moment. Cheers, On Mon, Feb 3, 2020 at 11:51 AM Simon Weller wrote: > All, > > During the 2019 CCC @ Apachecon North America, a few of us discussed the > need for a new Software Defined Networking (SDN) integration for > CloudStack, now that Nuage has chosen to depreciate their SDN product > portfolio. > I've been working closely with Sven Vogel on outlining how we might be > able to start a Special Interest Group (SIG) to design and build an ACS > network plugin into the Linux Foundation project Tungsten Fabric (Formally > known as Open Contrail). > > Both Sven's company, EWERK and my company ENA are willing to contribute > developers to this effort, as we feel it's important for Apache CloudStack > to have a robust SDN option that utilizes a well known and stable open > source SDN project and one that is community supported. > Although there is an existing plugin for Contrail that was originally > contributed by Juniper, it has been orphaned in the ACS code base for many > years and to my knowledge, it’s unusable. > Over the years, we've had a number of SDN integrations come and go. This > has left users in the lurch and discouraged other potential companies from > considering these options, as one has to be confident in the longevity of > the plugin. > > Why Tungsten Fabric? > Tungsten Fabric has been around for quite a while and it is now officially > a Linux Foundation project, so it has a considerable amount of support > behind it. It's scalable, multi-tenant, supports a number of advanced > security features, as well a large chunk of built in components we > currently need a Virtual Router to provide. > It's dual stack IPV4 and IPV6 and heavily utilizes BGP and MPLS. This > makes it ideal for those of us that maintain our own networks, as it will > provide tight integration options and eliminate the need for complicated > Private Gateway (PG) setups for VPCs. > Additionally, with service stitching and EVPN capabilities, it will make > it a lot easier for operators to support other platforms without having to > build a dedicated plugin, or figure out how to support those network or > security features through other L2/L3 hacks. > > Sven and I would like to gauge feedback from the community on this > proposal and see whether other organizations are interested in > participating. > > Thanks, > > Sven and Simon >
Re: [PRIMATE][SIG] Meeting Notes
10 Feb 2020 meeting notes: Project board: https://github.com/apache/cloudstack-primate/projects/1 Est. total effort left: ~40 hours Progress by number of supported APIs: ~98% (10 remaining APIs vs 461 APIs in old UI) High-level changes since last week: * VPC and related tabs/views including a new infrastructure section on ILBVM * Template, ISO, volume upload forms with a progress bar * IP range management for traffic types: public, management and storage * Many pending tabs for zone, isolated network etc. * Support for UI-wide pagination and table to display data in action forms On a high level, the only major tasks left are (1) VM deployment wizard (with Hoang/Sven), and (2) zone deployment wizards (with Rohit/Pearl). For all other features and components, we've pull requests pending review and testing: https://github.com/apache/cloudstack-primate/pulls Actions and goals are to continue to work on issues from the project board to completion of major tasks wrt the technical preview. Manual QA/test plan was discussed and my ShapeBlue colleagues have already started it since last week. Regards, Rohit Yadav Software Architect, ShapeBlue https://www.shapeblue.com From: Rohit Yadav Sent: Tuesday, February 4, 2020 13:56 To: dev@cloudstack.apache.org Subject: Re: [PRIMATE][SIG] Meeting Notes 3 Feb 2020 meeting notes: Project board: https://github.com/apache/cloudstack-primate/projects/1 Est. total effort left: ~70 hours Progress by number of supported APIs: ~95% (27 remaining APIs vs 461 APIs in old UI) High-level changes since last week: * VPC views and tabs (in progress) * Physical network, traffic type views/management, form, and tabs On a high level, the only major tasks left are: (1) VPC tabs/view/actions completion (with Rohit/Ritchie), (2) VM deployment wizard (with Hoang/Sven), and (3) zone deployment wizards (with Rohit/Pearl). For all other features and components, we've pull requests pending review and testing: https://github.com/apache/cloudstack-primate/pulls Actions and goals for this and the next week are to continue to work on issues from the project board to completion of major tasks wrt the technical preview. Manual QA/test plan was discussed and my ShapeBlue colleagues will start it this week. We're still exploring test automation methodologies. Regards, Rohit Yadav Software Architect, ShapeBlue https://www.shapeblue.com From: Rohit Yadav Sent: Monday, January 27, 2020 19:18 To: dev@cloudstack.apache.org Cc: Wido Hollander Subject: Re: [PRIMATE][SIG] Meeting Notes 27 Jan 2020 meeting notes: Project board: https://github.com/apache/cloudstack-primate/projects/1 Est. total effort left: ~100 hours Progress by number of supported APIs: ~90% (44 remaining APIs vs 461 APIs in old UI) High-level changes since last week: * Received a public VM (community-managed) for Primate QA/testing purposes from Wido/PCExtreme (Thanks Wido!) * Guest network actions tabs, egress, fw, pf, lb, vpn and SG egress/ingress * Add/import LDAP account for * Add host/pod/cluster form with option to dedicate to an account/domain * Enable SNAT for VM form * Add secondary storage form * Physical network, traffic type views/management, form and tabs * Dedicate VLAN/VNI range to account/project form * Zone resource capacity tab * VMware zone form, view * Work in progress: https://github.com/apache/cloudstack-primate/pulls Actions and goals for the next two weeks are to continue to work on issues from the project board, work towards manual QA and test automation. Regards, Rohit Yadav Software Architect, ShapeBlue https://www.shapeblue.com From: Rohit Yadav Sent: Monday, January 20, 2020 20:56 To: dev@cloudstack.apache.org Subject: Re: [PRIMATE][SIG] Meeting Notes 20 Jan 2020 meeting notes: Project board: https://github.com/apache/cloudstack-primate/projects/1 Est. total effort left: ~150 hours Progress by number of supported APIs: ~81% (88 remaining APIs vs 461 APIs in old UI) High-level changes since last week: * Resource view and styling changes * Recurring snapshot schedule and take snapshot action form * Support for LDAP configuration management * Minor bug fixes and enhancements * In review - guest network tabs/actions, add network form, ldap account form, dedicated resource component, add cluster&host form * Work in progress: https://github.com/apache/cloudstack-primate/pulls Actions and goals for the next two weeks are to continue to work on issues from the project board, work towards manual QA and test-automation. Regards, Rohit Yadav Software Architect, ShapeBlue https://www.shapeblue.com From: Rohit Yadav Sent: Tuesday, January 14, 2020 15:11 To: dev@cloudstack.apache.org Subject: Re: [PRIMATE][SIG] Meeting Notes 14 Jan 2020
[GitHub] [cloudstack-primate] utchoang commented on issue #146: [WIP] Feature/vm wizard
utchoang commented on issue #146: [WIP] Feature/vm wizard URL: https://github.com/apache/cloudstack-primate/pull/146#issuecomment-584467673 @rhtyd cc @svenvogel This is my new design of the layout collapse mode to steps mode. Please review and let me know your comments.    This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] [cloudstack-primate] Pearl1594 opened a new pull request #154: [WIP] VPC: Add Internal LB form and Assign VM to LB rule form
Pearl1594 opened a new pull request #154: [WIP] VPC: Add Internal LB form and Assign VM to LB rule form URL: https://github.com/apache/cloudstack-primate/pull/154 -> Added collapsable view for Internal LB, Public IPs, SNAT and VMs -> Form for assigning VMs to Internal LBs This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
JDK Changes
All, Master/4.14 will soon require that JDK11 (https://github.com/apache/cloudstack/pull/3601) is available for building and running management server, usage server and the KVM agent. Like the previous transition from JDK6 to JDK7, and then JDK7 to JDK8, it is advised to install JDK11 on your development workstation and setup and use latest maven 3.6.3+ and jenv (https://www.jenv.be/) and on checking out the branches it will automatically detect, switch and use suitable JDK version. Developers may build the 4.14 systemvmtemplate with openjdk11-headless using qemu+packer, or get from here: http://download.cloudstack.org/systemvm/4.14/ For users, the deb/pkg will ensures that openjdk11 will be installed (and on unsupported/old distributions that don't have JDK11, external repositories or ppa from openjdk, Azul etc may be used) but on in-place upgrades post-installation users need to verify that JDK11 is the default JDK in their environments. This will be documented as part of the release/upgrade notes (https://github.com/apache/cloudstack-documentation/pull/87/files). Any questions, concerns, feedback? Thanks. Past discussions references: https://markmail.org/message/6nnlxdh3zjenqjrx https://markmail.org/message/wygk547geecfypcq Regards, Rohit Yadav Software Architect, ShapeBlue https://www.shapeblue.com rohit.ya...@shapeblue.com www.shapeblue.com 3 London Bridge Street, 3rd floor, News Building, London SE1 9SGUK @shapeblue