Agenda for Networking Meeting -- 2016-05-18 @ 16:00 UTC

[gundalow]

Please add items to this ticket with your IRC name (if different to your GitHub)

FYI @privateip

[gundalow]

< kei> ansible/ansible#15911 @keinohguchi

[keithnoguchi]

Can we discuss about PR 15911, OpenSwitch REST authentication fix?

ansible/ansible#15911

It's a cookie based auth, enabled sometime back and, we didn't update here on ansible side. With this
fix, can we issue rest call through ops_facts.py, as shown in the following travis CI, which using my level branch with the fix:

https://travis-ci.org/keinohguchi/dc-on-docker/jobs/131047764

Chat today!

[christx2]

Hello, we would like to propose an SDN repo under the core modules:
https://github.com/ansible/ansible-modules-core/tree/devel/network/sdn

this would contain SDN overaly modules that can create entire constructs for a network topology
precisely as an Application owner would like to see them, example:

1. Create a Layer 2 or Layer 3 Topology - Domains, Availability zones, Subnets, virtual ports and all the IP space required for this
2. Create all the ACL Policies for above (Ingress and Egress)
3. Create all the Quality of Service for above
4. Create Gateways and Inter Domain relationships (Containerized applications could leverage this)
5. Make all of the above immutable and entirely portable for SDN underpinning for applications consuming this set of modules via their respective .yml template.

This would not be Fabric provisioning or Device Configuration, and therefore require a separate repo for inclusion into core modules for SDN (Software Defined Networking) where functionality is coded directly into the Overlay Network.

Thanks,
c

[keithnoguchi]

Thank you, @privateip, as we have PR #15911 merged into devel. I've create another one, ansible/ansible-modules-core#3693 ops_template.py fix under core module, for @privateip to review.

I'll be in the meeting anyway. :)

Cheers,

[privateip]

Ansible network facts subsets

all
hardware
config
interfaces

net_facts

subset: all (default)

• ansible_net_gather_subset
• ansible_net_model
• ansible_net_version
• ansible_net_hostname
• ansible_net_image
• ansible_net_serialnum

subset: hardware

• ansible_net_filesystems
• ansible_net_memfree_mb
• ansible_net_memtotal_mb

subset: config

• ansible_net_config

subset: interfaces

• ansible_net_all_ipv4_addresses: []
• ansible_net_all_ipv6_addresses: [
• * ansible_net_interfaces: <ansible_net_interfaces>
• ansible_net_neighbors: <ansible_net_neighbors>

ansible_net_interfaces

• {key: name}
  • macaddress
  • ipv4
    • address
    • netmask
  • ipv6
    • address
    • prefix
  • mtu
  • bandwidth
  • mediatype
  • duplex
  • type
  • lineprotocol
  • operstatus

ansible_net_neighbors

• {key: name}
  • host
  • port

[gundalow]

@privateip I've created the new agenda ticket, however I didn't want to close this one as I wasn't sure if everything had been recorded.

We can chat on IRC before then regarding how you like to run these, if that would help?

New agenda for 25th May #101

[gundalow]

Meeting complete