search for: networkdevice

Created a new class to represent network interface devices, named NetworkDeviceAgent. Signed-off-by: Darryl L. Pierce <dpierce at redhat.com> --- src/Makefile.am | 9 +- src/host.cpp | 26 +++-- src/host.h | 4 +- src/linux_platform.cpp | 70 +++++++++++ src/linux_platform.h | 4 + src/networkdevice.cpp | 49 ++++++++ src/...

In looking at the code I realized that the last of the HAL depenencies were removed with this patch. So, I'm pushing an updated patch that contains none of the HAL code in it.

...ace _qmf = qmf::com::redhat::matahari; - void -HostAgent::setup(ManagementAgent* agent) +Host::set_uuid(const string uuid) { - management_object = new _qmf::Host(agent, this); - agent->addObject(management_object); - - // discover the aspects of the host - processors.setup(agent, this); - networkdevices = Platform::instance()->get_network_devices(); - - for(vector<NetworkDeviceAgent>::iterator iter = networkdevices.begin(); - iter != networkdevices.end(); - iter++) - { - iter->setup(agent, this); - } + _uuid = uuid; +} - struct utsname details; - string uuid...

...at it should represent all network devices, including virtual interfaces, bridges, etc. So what I was thinking about was to have an agent to represent the physical device, and then agents under it to represent the network(s) to which it is associated. So the physical device would represented by a NetworkDevice agent with the following properties/methods: * mac_address - address for device * vendor - the NIC manufacturer * model - the NIC model * interface - the system iface name * create() - creates a network definition * destroy() - deletes the network definition * blink()...

Refactoring the previous patch ended up creating two deltas. This patch pushes them both together into a single commit.

...cessorslistener.h delete mode 100644 src/qmf/processorsagent.cpp delete mode 100644 src/qmf/processorsagent.h diff --git a/src/Makefile.am b/src/Makefile.am index 498ee72..7daea07 100644 --- a/src/Makefile.am +++ b/src/Makefile.am @@ -9,9 +9,7 @@ generated_file_list = \ qmf/com/redhat/matahari/NetworkDevice.cpp \ qmf/com/redhat/matahari/NetworkDevice.h \ qmf/com/redhat/matahari/Package.cpp \ - qmf/com/redhat/matahari/Package.h \ - qmf/com/redhat/matahari/Processors.cpp \ - qmf/com/redhat/matahari/Processors.h + qmf/com/redhat/matahari/Package.h nodist_matahari_SOURCES = $(generated_file_list) $...

The previous patch, for whatever reason, fails to apply on top of tip. This patch is reimplemented and, hopefully, fixed.

...grep G UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 Destination Gateway Genmask Flags Metric Ref Use Iface 0.0.0.0 192.168.X.Y 0.0.0.0 UG 10 0 0 eth0 [0] http://www.cyberciti.biz/faq/rhel-fedora-centos-setup-routing-metric-networkdevice/ [1] https://access.redhat.com/knowledge/docs/en-US/Red_Hat_Enterprise_Linux/5/html/Deployment_Guide/s1-networkscripts-interfaces.html [2] https://access.redhat.com/knowledge/docs/en-US/Red_Hat_Enterprise_Linux/6/html/Deployment_Guide/s1-networkscripts-interfaces.html Have a great day, -- ---~~....

Hello all, Does anyone currently manage Cisco ASA''s out there via Puppet, if so how ? Due to the size of our network it would be great if Puppet could manage Object-groups and ACL''s etc to try and standardize across our ASA hosts. e.g. On one ASA an Object-group would be called monitoring_server on another ASA mon_srv another ASA monsrv It makes understanding the

Hi, I''m using Amazon EC2 and I''m planning to use puppet to deploy automatically my instances, however, I have an issue I can''t rely think through. As most people advised, I used a DNS server (bind to be precise) so that my instances can register to it but also ask this DNS Server the IP of the puppetmaster. However, as this DNS server is also running on Amazon EC2

This introduces support to run P2V without X server. Runtime parameters are specified via kernel command line making it hopefully suitable for automated migration with a little help of PXE boot. Patchset is not squashed and represents dev. history.