Changes between Version 21 and Version 22 of CloudNativeRenew

Timestamp:

Mar 28, 2021, 10:26:17 PM (4 years ago)

Author:

roewekamp

Comment:

--

CloudNativeRenew

@@ -37 +37 @@
  * You can also create a shadow net system yourself: Open up a Renew instance (or use the one spawned by the startup earlier), draw a reference net (or multiple), save all of your nets with a specific name each (File -> Save Drawing As...), and hit File -> Export -> Export all drawings (merged file) -> !ShadowNetSystem
    Close the net drawing(s), but not Renew itself.
-* Assume the shadow net system file is namend `primes.sns`: Upload the net using:\\ `curl -F 'snsZipFile=@primes.sns' localhost:8085/upload/sns?fileName=primes.sns`
+* Assume the shadow net system file is namend `primes.sns`: Upload the net using:\\ `curl -F "snsZipFile=@primes.sns" localhost:8085/upload/sns?fileName=primes`
 * After uploading you can start a simulation. Assume you named the main net within `primes.sns`: `primeDistributor`.
- * Use this command: `curl -X POST 'localhost:8085/simulation/start?mainNet=primeDistributor&sns=primes.sns'` \\
+ * Use this command: `curl -X POST "localhost:8085/simulation/start?mainNet=primeDistributor&sns=primes.sns"` \\
    Note, that shadow net systems do not hold graphical information, therefore you will not be able to see the simulation within the spawned Renew instance, but you should be able to observe the console output generated by the running simulation.
    Within the intended deployment, that was shown in the figure above, Renew instances are headless anyways and do not have any graphical output.