https://github.com/outscale/osc-ricochet-2

A incomplete local Outscale cloud stack. Develop and test your cloud apps offline
https://github.com/outscale/osc-ricochet-2

Last synced: 7 days ago
JSON representation

A incomplete local Outscale cloud stack. Develop and test your cloud apps offline

• Host: GitHub
• URL: https://github.com/outscale/osc-ricochet-2
• Owner: outscale
• License: bsd-3-clause
• Created: 2024-02-22T14:53:14.000Z (9 months ago)
• Default Branch: master
• Last Pushed: 2024-11-04T16:17:46.000Z (8 days ago)
• Last Synced: 2024-11-04T16:23:54.793Z (8 days ago)
• Language: Rust
• Homepage:
• Size: 216 KB
• Stars: 0
• Watchers: 5
• Forks: 0
• Open Issues: 2
• Metadata Files:
  • Readme: README.md
  • License: LICENSE

Awesome Lists containing this project

README

        
[![Project Sandbox](https://docs.outscale.com/fr/userguide/_images/Project-Sandbox-yellow.svg)](https://docs.outscale.com/en/userguide/Open-Source-Projects.html)

# osc-ricochet-2

not a vaporware, but a cloudy stuff, about sending back request from where it come from.

using this project, while expecting the same result as outscale API, might have unforeseen consequences.

but you're a free man, so you can try.

# configuration

if you want Ricochet to Rise and Shine, you need to have the right conf in the right place.

1rst argumnent of ricochet is the configuration path.

Example:

```json

{

     // either exist, full, mix or none, none ignore all auth, exist, check if the user exist but don't go futher,

     // and full do the full auth, full is buggy. mix check password, but not the V4 signature.

    "auth_type": "headarches",

    "tls": false, // start the server as an http/https server

    "in_convertion": true, // support for FCU/ICU and other non outscale API (just support a very few call so far)

    "password_as_ak": true, // password auth, is now consider as strong as ak/sk

    "users": [ // Can have multiple users

	{

	    "access_key": "11112211111110000000",

	    "secret_key": "0000001111112222223333334444445555555666",

	    "login": "joe",

	    "pass": "ashita wa dochida"

	},

	{

	    "access_key": "11112211111110000333",

	    "secret_key": "1000001111112222223333334444445555555666",

	    "login": "titi",

	    "pass": "toto"

	}

    ]

}

```

# build

```

cargo build

```

# usage

```

cargo run [-- CONFIG.json]

```

for config see [this](./ricochet-headarches.json) and [that](./ricochet.json) as example

# Logs Management

## Set Logs in config

```json

{

	"log": {

		"scope": ["nets", "vms"],

		"dir": "all"

	}

}

```

## Set Logs at runtime

`"scope"` is an array of what resources you want to log, like `["nets", "vms"]`

`"dir"` is used to set if you want to see input or output arguments, either `"in", "out" or "all"`

Example:

```bash

curl 127.0.0.1:3000/SetLog_ -d '{"log": {"scope": ["nets"], "dir": "in"}}'

```

# ASCII Art

```

[oapi-cli]

    |

    V

(createVms)    ->    [ricochet-2]

                           |

                           V

                     (create a VM)

                           |

                           V

[oapi-cli]    <----   (Send return)

    |

    V

(Print Result)

------- Some time later with a different client ----

 [curl]

    |

    V

(ReadVms)      ->    [ricochet-2]

                         |

                         V

 [curl]     <- (Send earlier created VM)

    |

    V

(print result)

```

# contribution

You can open a PR, or an issue