Hi,
We've stared on the automation journey some time ago. These are just some
generic subjects that you might have to think about:
1. What to automate
There are many different types of 'automation' out there. We currently
concentrate on 'orchestration' of product instances and on 'automation' of
> Of Antti Ristimäki
> Sent: Sunday, August 19, 2018 4:17 PM
> To: juniper-nsp
> Subject: Re: [j-nsp] Network automation vs. manual config
>
> Hi,
>
> Thank you all for your comments both on and off the list. A lot of food for
> thoughts. I can see that many of you h
is registered with the Chamber of Commerce in
> Amsterdam with registration number 40535155 and operates in the UK as a branch
> of GÉANT Vereniging. Registered office: Hoekenrode 3, 1102BR Amsterdam, The
> Netherlands. UK branch address: City House, 126-130 Hills Road, Cambridge CB2
> 1PQ, UK.
>
Antti Ristimäki wrote:
So, now that more and more of us are automating their network, there will
> be the question about how to manage the configurations, if they are
> partially automated and partially manually maintained.
>
...
One option is to generate the whole config [...]
>
...
Another
> On 20/08/2018, at 12:43 AM, Thomas Bellman wrote:
>
> On 2018-08-19 08:11, Nathan Ward wrote:
>
>> I would be interested in a way to build a command alias with
>> `| display inheritance | display commit-scripts | display omit | exclude #`
>> or something - `exclude #` isn’t the best either,
On 2018-08-19 08:11, Nathan Ward wrote:
> I would be interested in a way to build a command alias with
> `| display inheritance | display commit-scripts | display omit | exclude #`
> or something - `exclude #` isn’t the best either, as # is often in int
> description etc.
Slightly aside: instead
Hi,
> On 18/08/2018, at 1:06 AM, Michael Still wrote:
>
> Side note on apply groups and display inheritance. I've submitted a Juniper
> ER for an enhancement to have the ability to have ' | display inheritance'
> a 'default' cli behavior (configurable via 'set cli display-inheritance'
> option
We have daily work to configure basic load balancer, customer certs and open
firewalls, daily 5-15 tickets, without some sort of automation that will be
waste a lot of resources for Sr people. So I used ansible and some python and
shell script.
Also considering to use Yaml, Jinja2 for standard
2018 14:06
To: juniper-nsp@puck.nether.net
Subject: Re: [j-nsp] Network automation vs. manual config
Side note on apply groups and display inheritance. I've submitted a Juniper ER
for an enhancement to have the ability to have ' | display inheritance'
a 'default' cli behavior (configurable via 'set
Side note on apply groups and display inheritance. I've submitted a Juniper
ER for an enhancement to have the ability to have ' | display inheritance'
a 'default' cli behavior (configurable via 'set cli display-inheritance'
option that is defaulted to off). I've also asked for a login-class option
> On 17/08/2018, at 10:54 PM, Antti Ristimäki wrote:
>
> Another option is to apply the auto-generated configuration via apply-groups
> and apply all manual configurations explicitly so that the automatic and
> manual configurations merge with each other. The positive side of this
> approach
On Fri, Aug 17, 2018 at 07:45:12AM -0400, Jason Lixfeld wrote:
> Maybe I’m missing an implied exception, but every once in a while one
> needs to make some sort of manual configuration to resolve a time
> sensitive some corner case that the provisioning system doesn’t
> support because someone
Dear Antti,
On Fri, Aug 17, 2018 at 01:54:27PM +0300, Antti Ristimäki wrote:
> This is something that I've been thinking quite a lot, so I would be
> delighted to hear some comments, experiences or recommendations.
>
> So, now that more and more of us are automating their network, there
> will
I’ll admit that I haven’t done much automation yet, so take this with a grain
of salt and provide clue where required...
> On Aug 17, 2018, at 6:54 AM, Antti Ristimäki wrote:
>
> Hi colleagues,
>
> This is something that I've been thinking quite a lot, so I would be
> delighted to hear some
Hi colleagues,
This is something that I've been thinking quite a lot, so I would be delighted
to hear some comments, experiences or recommendations.
So, now that more and more of us are automating their network, there will be
the question about how to manage the configurations, if they are
15 matches
Mail list logo
