Automation

It's a theoretical maximum.

However, the point is that when your Juniper state is controlled by automation, you don't have to wait for 90 seconds (on some SRXs for example) for a single change.
Also the logic to which an application may be configured, is such that a change that you may do in one commit via CLI, is called over separate functions which each require their own commit. For example, you may have a device with 96 ports that you are provisioning, however you are only configuring 10 of those ports, but the remaining 86 may have some basic interface-name disable unit 0 family ethernet-switching configuration applied.
Instead of one commit to apply the config to all 96 ports, your tool might do each interface individually, thus creating ~96 changes.

Conversely, you may deal with many, many LSPs and may want to make batch changes, but again, perhaps the program only does 1 LSP at a time.

Maybe you have a device with logical systems that is controlled by automation whereby multiple clients cause configuration changes to be made, it's useful for the API to make multiple changes very quickly in this situation.

Cheers,

------------------------------
ANDREY LEO
------------------------------

Original Message:
Sent: 08-16-2022 11:08
From: Unknown User
Subject: Question on the JET API

Hi.

 

Juniper documentation says that automation using the JET API allows you to perform thousands of commits a second.

 

In what scenario would I ever need such frequent commits?

 

 

Thanks,

Deepak

Juniper Business Use Only

Thanks Andrey!
Original Message:
Sent: 08-17-2022 07:32
From: ANDREY LEO
Subject: Question on the JET API

It's a theoretical maximum.

However, the point is that when your Juniper state is controlled by automation, you don't have to wait for 90 seconds (on some SRXs for example) for a single change.
Also the logic to which an application may be configured, is such that a change that you may do in one commit via CLI, is called over separate functions which each require their own commit. For example, you may have a device with 96 ports that you are provisioning, however you are only configuring 10 of those ports, but the remaining 86 may have some basic interface-name disable unit 0 family ethernet-switching configuration applied.
Instead of one commit to apply the config to all 96 ports, your tool might do each interface individually, thus creating ~96 changes.

Conversely, you may deal with many, many LSPs and may want to make batch changes, but again, perhaps the program only does 1 LSP at a time.

Maybe you have a device with logical systems that is controlled by automation whereby multiple clients cause configuration changes to be made, it's useful for the API to make multiple changes very quickly in this situation.

Cheers,

------------------------------
ANDREY LEO

Original Message:
Sent: 08-16-2022 11:08
From: Unknown User
Subject: Question on the JET API

Hi.

 

Juniper documentation says that automation using the JET API allows you to perform thousands of commits a second.

 

In what scenario would I ever need such frequent commits?

 

 

Thanks,

Deepak

Juniper Business Use Only

You're welcome :)

------------------------------
ANDREY LEO
------------------------------

Original Message:
Sent: 08-17-2022 11:44
From: Unknown User
Subject: Question on the JET API

Thanks Andrey!
Original Message:
Sent: 08-17-2022 07:32
From: ANDREY LEO
Subject: Question on the JET API

It's a theoretical maximum.

However, the point is that when your Juniper state is controlled by automation, you don't have to wait for 90 seconds (on some SRXs for example) for a single change.
Also the logic to which an application may be configured, is such that a change that you may do in one commit via CLI, is called over separate functions which each require their own commit. For example, you may have a device with 96 ports that you are provisioning, however you are only configuring 10 of those ports, but the remaining 86 may have some basic interface-name disable unit 0 family ethernet-switching configuration applied.
Instead of one commit to apply the config to all 96 ports, your tool might do each interface individually, thus creating ~96 changes.

Conversely, you may deal with many, many LSPs and may want to make batch changes, but again, perhaps the program only does 1 LSP at a time.

Maybe you have a device with logical systems that is controlled by automation whereby multiple clients cause configuration changes to be made, it's useful for the API to make multiple changes very quickly in this situation.

Cheers,

------------------------------
ANDREY LEO

Original Message:
Sent: 08-16-2022 11:08
From: Unknown User
Subject: Question on the JET API

Hi.

 

Juniper documentation says that automation using the JET API allows you to perform thousands of commits a second.

 

In what scenario would I ever need such frequent commits?

 

 

Thanks,

Deepak

Juniper Business Use Only