<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=Windows-1252">
</head>
<body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; color: rgb(0, 0, 0); font-size: 14px; font-family: Calibri, sans-serif;">
<div>Hi All:</div>
<div><br>
</div>
<div>Thanks Kevin. David, yes I think we have a model that will work for u and would definitely want to discuss this more with u. I do hope that this can also help refine some of our thoughts. U can join us in our weekly IRC [1] (next one is tomorrow) and we
can create an agenda item for more discussion. If the time is inconvenient, pls reach out to me and we set a time for a discussion with the team.</div>
<div><br>
</div>
<div>[1] <a href="http://eavesdrop.openstack.org/#Firewall_as_a_Service_(FWaaS)_Team_Meeting">http://eavesdrop.openstack.org/#Firewall_as_a_Service_(FWaaS)_Team_Meeting</a></div>
<div><br>
</div>
<div>Thanks</div>
<div><br>
</div>
<div>Sridar</div>
<div><br>
</div>
<span id="OLK_SRC_BODY_SECTION">
<div style="font-family:Calibri; font-size:11pt; text-align:left; color:black; BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; PADDING-BOTTOM: 0in; PADDING-LEFT: 0in; PADDING-RIGHT: 0in; BORDER-TOP: #b5c4df 1pt solid; BORDER-RIGHT: medium none; PADDING-TOP: 3pt">
<span style="font-weight:bold">From: </span>Kevin Benton <<a href="mailto:kevin@benton.pub">kevin@benton.pub</a>><br>
<span style="font-weight:bold">Reply-To: </span>OpenStack List <<a href="mailto:openstack-dev@lists.openstack.org">openstack-dev@lists.openstack.org</a>><br>
<span style="font-weight:bold">Date: </span>Monday, October 31, 2016 at 2:59 PM<br>
<span style="font-weight:bold">To: </span>OpenStack List <<a href="mailto:openstack-dev@lists.openstack.org">openstack-dev@lists.openstack.org</a>><br>
<span style="font-weight:bold">Subject: </span>Re: [openstack-dev] [neutron] Cloud Provider Security Groups<br>
</div>
<div><br>
</div>
<div>
<div>
<div dir="ltr">I believe the FWaaS v2 work is attempting to capture this concept of provider-set rules to address this very use-case.
<div><br>
</div>
<div>One of the items from the spec[1] sounds closely related:</div>
<div><br>
</div>
<div>'Adds an explicit action attribute to rules so that "deny" and "reject" actions can be specified in addition to the existing "allow" action. This is particularly important for tenant or service provider network admins that specify firewall policies meant
to apply to all of a tenant's or service provider's instances, regardless of application.'<br>
</div>
<div><br>
</div>
<div>1. <a href="https://github.com/openstack/neutron-specs/blob/master/specs/newton/fwaas-api-2.0.rst">https://github.com/openstack/neutron-specs/blob/master/specs/newton/fwaas-api-2.0.rst</a></div>
</div>
<div class="gmail_extra"><br>
<div class="gmail_quote">On Mon, Oct 31, 2016 at 5:28 PM, David G. Bingham <span dir="ltr">
<<a href="mailto:dbingham@godaddy.com" target="_blank">dbingham@godaddy.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div style="word-wrap:break-word;color:rgb(0,0,0);font-size:14px;font-family:Calibri,sans-serif">
<div>
<div id="m_7767359750337862623magicdomid4" style="margin:0px;padding:0px;font-family:'Helvetica Neue',Arial,sans-serif;font-size:12px;font-variant-ligatures:normal">
<span style="margin:0px;padding:1px 0px">Yo Neutron devs :-)</span></div>
<div id="m_7767359750337862623magicdomid5" style="margin:0px;padding:0px;font-family:'Helvetica Neue',Arial,sans-serif;font-size:12px;font-variant-ligatures:normal">
<br style="margin:0px;padding:0px">
</div>
<div id="m_7767359750337862623magicdomid1323" class="m_7767359750337862623ace-line" style="margin:0px;padding:0px;font-family:'Helvetica Neue',Arial,sans-serif;font-size:12px;font-variant-ligatures:normal">
<span style="margin:0px;padding:1px 0px">I was wondering if something like the following subject has come up: "Cloud-provider Security Groups”.</span></div>
<div id="m_7767359750337862623magicdomid1323" class="m_7767359750337862623ace-line" style="margin:0px;padding:0px;font-family:'Helvetica Neue',Arial,sans-serif;font-size:12px;font-variant-ligatures:normal">
<span style="margin:0px;padding:1px 0px"><br>
</span></div>
<div id="m_7767359750337862623magicdomid1323" class="m_7767359750337862623ace-line" style="margin:0px;padding:0px;font-family:'Helvetica Neue',Arial,sans-serif;font-size:12px;font-variant-ligatures:normal">
*Goal of this email*: Gauge the community’s need and see if this has come up in past.</div>
<div id="m_7767359750337862623magicdomid2020" class="m_7767359750337862623ace-line" style="margin:0px;padding:0px;font-family:'Helvetica Neue',Arial,sans-serif;font-size:12px;font-variant-ligatures:normal">
<span style="margin:0px;padding:1px 0px">*Requirement*: Apply a provider-managed global set of network flows to all instances.</span></div>
<div id="m_7767359750337862623magicdomid2021" class="m_7767359750337862623ace-line" style="margin:0px;padding:0px;font-family:'Helvetica Neue',Arial,sans-serif;font-size:12px;font-variant-ligatures:normal">
<span style="margin:0px;padding:1px 0px">*Use Case*: For our private cloud, have need to dynamically allow network traffic flows from other internal network sources across all instances.</span></div>
<div id="m_7767359750337862623magicdomid2022" class="m_7767359750337862623ace-line" style="margin:0px;padding:0px;font-family:'Helvetica Neue',Arial,sans-serif;font-size:12px;font-variant-ligatures:normal">
<span style="margin:0px;padding:1px 0px">*Basic Idea*: Provide an *admin-only* accessible security group ruleset that would persist and apply these "cloud-provider" security group rules to all instances of a cloud. This *may* be in the form of new "provider"
API or an extension to existing API only accessible via "admin". When instances are created, this global SG ruleset would be applied to each VM/ironic instance. This feature likely should be capable of being enabled/disabled depending on the provider's need.</span></div>
<div id="m_7767359750337862623magicdomid2027" class="m_7767359750337862623ace-line" style="margin:0px;padding:0px;font-family:'Helvetica Neue',Arial,sans-serif;font-size:12px;font-variant-ligatures:normal">
<span style="margin:0px;padding:1px 0px"><br>
</span></div>
<div id="m_7767359750337862623magicdomid2027" class="m_7767359750337862623ace-line" style="margin:0px;padding:0px;font-family:'Helvetica Neue',Arial,sans-serif;font-size:12px;font-variant-ligatures:normal">
<span style="margin:0px;padding:1px 0px">*Real example*: Company security team wants to audit consistent security software installations (i.e. HIPS) across our entire fleet of servers for compliance reporting. Each vm/ironic instance is required to have this
software installed and up to date. Security audit team actually audits each and every server to ensure it is running, patched and up to date. These auditing tools source from a narrow set of internal IPs/ports and each instance must allow access to these auditing
tools.</span></div>
<div id="m_7767359750337862623magicdomid21" style="margin:0px;padding:0px;font-family:'Helvetica Neue',Arial,sans-serif;font-size:12px;font-variant-ligatures:normal">
<br style="margin:0px;padding:0px">
</div>
<div id="m_7767359750337862623magicdomid2032" class="m_7767359750337862623ace-line" style="margin:0px;padding:0px;font-family:'Helvetica Neue',Arial,sans-serif;font-size:12px;font-variant-ligatures:normal">
<span style="margin:0px;padding:1px 0px">--- What we do today to hack a "cloud-provider" flow in a private cloud ---</span></div>
<div id="m_7767359750337862623magicdomid1802" class="m_7767359750337862623ace-line" style="margin:0px;padding:0px;font-family:'Helvetica Neue',Arial,sans-serif;font-size:12px;font-variant-ligatures:normal">
<span style="margin:0px;padding:1px 0px">1) We've locked down the default rules (only admins can modify which makes effectively kills a lot of canned neutron tools).</span></div>
<div id="m_7767359750337862623magicdomid1803" class="m_7767359750337862623ace-line" style="margin:0px;padding:0px;font-family:'Helvetica Neue',Arial,sans-serif;font-size:12px;font-variant-ligatures:normal">
<span style="margin:0px;padding:1px 0px">2) We've written an external script that iterates over all projects in our private cloud (~10k projects)</span></div>
<div id="m_7767359750337862623magicdomid1804" class="m_7767359750337862623ace-line" style="margin:0px;padding:0px;font-family:'Helvetica Neue',Arial,sans-serif;font-size:12px;font-variant-ligatures:normal">
<span style="margin:0px;padding:1px 0px">3) For each project:</span></div>
<div id="m_7767359750337862623magicdomid1805" class="m_7767359750337862623ace-line" style="margin:0px;padding:0px;font-family:'Helvetica Neue',Arial,sans-serif;font-size:12px;font-variant-ligatures:normal">
<span style="margin:0px;padding:1px 0px">3a) Fetch default SGs for that project and do a comparison of its default rules against *target* default rules</span></div>
<div id="m_7767359750337862623magicdomid1806" class="m_7767359750337862623ace-line" style="margin:0px;padding:0px;font-family:'Helvetica Neue',Arial,sans-serif;font-size:12px;font-variant-ligatures:normal">
<span style="margin:0px;padding:1px 0px">3b) Create any new missing rules, delete any removed rules</span></div>
<div id="m_7767359750337862623magicdomid1807" class="m_7767359750337862623ace-line" style="margin:0px;padding:0px;font-family:'Helvetica Neue',Arial,sans-serif;font-size:12px;font-variant-ligatures:normal">
<span style="margin:0px;padding:1px 0px">3c) Next project</span></div>
<div id="m_7767359750337862623magicdomid1808" class="m_7767359750337862623ace-line" style="margin:0px;padding:0px;font-family:'Helvetica Neue',Arial,sans-serif;font-size:12px;font-variant-ligatures:normal">
<span style="margin:0px;padding:1px 0px">This process is cumbersome, takes 20+ hours to run (over ~10k projects) and has to be throttled such that it doesn't over-hammer neutron while its still serving production traffic.</span></div>
<div id="m_7767359750337862623magicdomid30" style="margin:0px;padding:0px;font-family:'Helvetica Neue',Arial,sans-serif;font-size:12px;font-variant-ligatures:normal">
<br style="margin:0px;padding:0px">
</div>
<div id="m_7767359750337862623magicdomid1809" class="m_7767359750337862623ace-line" style="margin:0px;padding:0px;font-family:'Helvetica Neue',Arial,sans-serif;font-size:12px;font-variant-ligatures:normal">
<span style="margin:0px;padding:1px 0px">--- What we'd like to do in future ---</span></div>
<div id="m_7767359750337862623magicdomid1810" class="m_7767359750337862623ace-line" style="margin:0px;padding:0px;font-family:'Helvetica Neue',Arial,sans-serif;font-size:12px;font-variant-ligatures:normal">
<span style="margin:0px;padding:1px 0px">1) Call Security Group API that would modify a "cloud-provider" ruleset.</span></div>
<div id="m_7767359750337862623magicdomid1811" class="m_7767359750337862623ace-line" style="margin:0px;padding:0px;font-family:'Helvetica Neue',Arial,sans-serif;font-size:12px;font-variant-ligatures:normal">
<span style="margin:0px;padding:1px 0px">2) When updated, agents on HVs detect the "cloud-provider" change and then apply the rules across all instances.</span></div>
<div id="m_7767359750337862623magicdomid1812" class="m_7767359750337862623ace-line" style="margin:0px;padding:0px;font-family:'Helvetica Neue',Arial,sans-serif;font-size:12px;font-variant-ligatures:normal">
<span style="margin:0px;padding:1px 0px">Naturally there are going to be a lot of technical hurdles to make this happen while a cloud is currently in-flight.</span></div>
<div id="m_7767359750337862623magicdomid35" style="margin:0px;padding:0px;font-family:'Helvetica Neue',Arial,sans-serif;font-size:12px;font-variant-ligatures:normal">
<br style="margin:0px;padding:0px">
</div>
<div id="m_7767359750337862623magicdomid1813" class="m_7767359750337862623ace-line" style="margin:0px;padding:0px;font-family:'Helvetica Neue',Arial,sans-serif;font-size:12px;font-variant-ligatures:normal">
<span style="margin:0px;padding:1px 0px">Other uses for “Provider SGs":</span></div>
<div id="m_7767359750337862623magicdomid1814" class="m_7767359750337862623ace-line" style="margin:0px;padding:0px;font-family:'Helvetica Neue',Arial,sans-serif;font-size:12px;font-variant-ligatures:normal">
<span style="margin:0px;padding:1px 0px">* We want to enable new shared features (i.e. monitoring aaS) that all our internal projects can take advantage of. When the monitoring team adds/modifies IPs to scale, we'd apply these cloud-provider rules on behalf
of all projects in the private cloud without users having concern themselves about the monitoring team's changes.</span></div>
<div id="m_7767359750337862623magicdomid1815" class="m_7767359750337862623ace-line" style="margin:0px;padding:0px;font-family:'Helvetica Neue',Arial,sans-serif;font-size:12px;font-variant-ligatures:normal">
<span style="margin:0px;padding:1px 0px">* We want to allow access to some internal sites to our VPN users on specific ports. These VPN ranges are dynamically changed by the VPN team. Our teams should not need to go into individual projects to add a new rule
when VPN team changes ranges.</span></div>
<div id="m_7767359750337862623magicdomid1816" class="m_7767359750337862623ace-line" style="margin:0px;padding:0px;font-family:'Helvetica Neue',Arial,sans-serif;font-size:12px;font-variant-ligatures:normal">
<span style="margin:0px;padding:1px 0px">* This list could go on and on and naturally makes much more sense in a *private cloud* scenario, but there may be cases for public providers.</span></div>
<div id="m_7767359750337862623magicdomid1534" class="m_7767359750337862623ace-line" style="margin:0px;padding:0px;font-family:'Helvetica Neue',Arial,sans-serif;font-size:12px;font-variant-ligatures:normal">
<br style="margin:0px;padding:0px">
</div>
<div id="m_7767359750337862623magicdomid1534" class="m_7767359750337862623ace-line" style="margin:0px;padding:0px;font-family:'Helvetica Neue',Arial,sans-serif;font-size:12px;font-variant-ligatures:normal">
I’d be happy to create a spec.</div>
<div id="m_7767359750337862623magicdomid1534" class="m_7767359750337862623ace-line" style="margin:0px;padding:0px;font-family:'Helvetica Neue',Arial,sans-serif;font-size:12px;font-variant-ligatures:normal">
<br>
</div>
<div id="m_7767359750337862623magicdomid1817" class="m_7767359750337862623ace-line" style="margin:0px;padding:0px;font-family:'Helvetica Neue',Arial,sans-serif;font-size:12px;font-variant-ligatures:normal">
<span style="margin:0px;padding:1px 0px">Seen this before? Thoughts? Good, Bad or Ugly? :-)</span></div>
<div id="m_7767359750337862623magicdomid1553" class="m_7767359750337862623ace-line" style="margin:0px;padding:0px;font-family:'Helvetica Neue',Arial,sans-serif;font-size:12px;font-variant-ligatures:normal">
<br style="margin:0px;padding:0px">
</div>
<div id="m_7767359750337862623magicdomid1818" class="m_7767359750337862623ace-line" style="margin:0px;padding:0px;font-family:'Helvetica Neue',Arial,sans-serif;font-size:12px;font-variant-ligatures:normal">
<span style="margin:0px;padding:1px 0px">Thanks,</span></div>
<div id="m_7767359750337862623magicdomid1819" class="m_7767359750337862623ace-line" style="margin:0px;padding:0px;font-family:'Helvetica Neue',Arial,sans-serif;font-size:12px;font-variant-ligatures:normal">
<span style="margin:0px;padding:1px 0px">David Bingham (wwriverrat on irc)</span></div>
<div id="m_7767359750337862623magicdomid1820" class="m_7767359750337862623ace-line" style="margin:0px;padding:0px;font-family:'Helvetica Neue',Arial,sans-serif;font-size:12px;font-variant-ligatures:normal">
<span style="margin:0px;padding:1px 0px">GoDaddy</span></div>
</div>
<div>
<div id="m_7767359750337862623MAC_OUTLOOK_SIGNATURE"></div>
</div>
</div>
<br>
______________________________<wbr>______________________________<wbr>______________<br>
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">
OpenStack-dev-request@lists.<wbr>openstack.org?subject:<wbr>unsubscribe</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/<wbr>cgi-bin/mailman/listinfo/<wbr>openstack-dev</a><br>
<br>
</blockquote>
</div>
<br>
</div>
</div>
</div>
</span>
</body>
</html>