Add iterator support to Resource Manager to enable this kind of thing:

for user in users:
if user.userclass == 'read-only':
user.deactivate()

For Junos release type "X", we need to decode the minor value into sub-values. "X44-D20" should be minor=(44,'D',20) ... or similar.

Add a utility object to support secure copy, ala paramiko SCP

remove all of the current imports from the init.py file. users will be required to explicitly import only what they need/want. will help improve usage/efficiency.

Need testing done on PhyPort object for MX and SRX-HE.

Presently only the main configuration is used. When retrieving information (like facts) from the device, we need to pull in the group (inherited) configurations as well.

Note that this will not write to apply-groups, only read from them.

Create a mechanism for folks to describe Tables and Views using YAML rather than coding in Python. This will help with the creation of these widgets and facilitate more operational state data out of the devices.

Include support for ssh-keys

Manage each of the policy rules.

Add dev.facts['HOME'] to store the home directory for the login user.

Create a Resource that models address books created at the [ security address-book] level.

admin@SegoLily-210# show security address-book
internet-address-book {
address dns-comcast-beaverton 68.87.69.150/32;
address dns-comcast-denver 68.87.85.102/32;
address-set dns-comcast-servers {
address dns-comcast-beaverton;
address dns-comcast-denver;
}
attach {
zone internet;
}
}
global {
address www.juniper.net 96.17.231.148/32;
address www.mirage.com 69.162.5.67/32;
}

For Resources that are managing other resources (like ZoneAddrBook), need to replace code to use new framework MANAGES class variable.

Renaming module namespace for "junos". Also changing toplevel "Netconf" class name to "Device".

NOW:
from jnpr.eznc import Netconf

FUTURE:
from jnpr.junos import Device

need the ability to have tables with composite key values; i.e. more than just "name" or a single value.

Routing-Engine Utilities

Support s/w upgrade process on:

• multi-RE MX
• EX-VC

Managing interfaces within zones

Add abstractions for handing simple static-NAT for bi-directional use-cases

For op Table, add selector to support tuple(name,View).

For example, get a view based on the table default view:
e0 = eths['ge-0/0/0']

Add ability:
e0 = eths[('ge-0/0/0', EthPortView2)]

selects 'ge-0/0/0' and uses view "EthPortView2".

Implement the "fact gathering" mechanism so folks can have easy access to common device attributes like serial-number, mac-address, etc.

Support for route and policy based VPNs, including resources for IKE, IPSEC, and ST interfaces.

So we can get to the specific bits of the version information, and to do comparison operations.

Hi,

Would like to execute the simple rpc like below without giving xml tags.

res = jdev.rpc("get-software-information")

The following code in netconf.py may fix that:

if isinstance(rpc_cmd, str):
  if rpc_cmd[0] != '<':
    rpc_cmd = '<' + rpc_cmd + '/>'
  rpc_cmd_e = etree.XML( rpc_cmd )

Thanks,
Sriram

For handling basic [edit security screen ...] type configuration

Need to verify Tables and Views on devices other than branch-SRX and EX4200. Looking for testing on MX, SRX-HE.

minor cleanup with implications. Need to stretch this change across a few releases to allow folks to make updates to their code.

warning exists now.

The :rpc: attribute is used to metaprogram RPC execution. For example if the Junos XML RPC is , you can use:

rsp = dev.rpc.get_chassis_inventory()

Or if an API takes parameters you pass them as key/value args. For example getting the status of an interface:

rsp = dev.rpc.get_interface_information(interface_name="ge-0/0/0")

Add "run state" (i.e. operational state) abstraction framework so folks that want to get the output of commands like "show interfaces media" get structured Python data and don't have to deal with Junos/XML.

The abstraction should be modelled as "database tables" and "table views".

Need an ability to dump a table/view to a complete dictionary so it can be exported as JSON.

Kinda a "cheater" function, but handy for debugging while in python interactive.

If the user parameter is omitted, then default to $USER environment variable.

For accessing the context (from-zone, to-zone) and gain access to managing the associate policy rules.

Adding the use of 'warnings.warn()' in code that will be deprecated due to namespace changes, etc.

YOU SHOULD RUN PYTHON with the "-Wall" command when testing your code to ensure you are not tripping over these deprecations.

see example "config-set.py" for the raw technique.

abstractions for handling basic source-NAT use-cases

Need handy routines to do fast & simply things like rollback, comit-check, etc.

Add utility class to facilitate software upgrades.

For jnpr.junos.op.loader, add the ability for the caller to pass existing global definitions so that the YAML files can create new definitions based from existing ones (extend) as well as pass in user defined functions.

More details on this as this functionality progresses.

Corresponding to [edit applications ...]

To better align the meaning with the function, the directory that was "resrc" will now be "cfg".

NOW:
from jnpr.eznc.cfg.user import *

WAS:
from jnpr.eznc.resc.user import *

RunstatView creation from YANG files??

Add options to the View YAML definition that allows folks to map a field value to True/False rather than returning a value.

For example, if the physical port has a field called "loopback" that will normally return back "enabled" or "disabled". Rather than returning this string value, return back True/False. Perhaps something like:

So rather than just the following that returns back 'enabled/disabled':

field : xpath

loopback : loopback

support this

loopback : { loopback : True=enabled }

Physical properties, not unit level configs - those will be separate resources.

helper function so you can do "cu.pdiff()" rather than "print cu.diff()".