Skip to content
This repository has been archived by the owner on Jun 12, 2024. It is now read-only.

Commit

Permalink
Update Opsani sign-up links
Browse files Browse the repository at this point in the history
Co-authored-by: Pavel Georgiev <[email protected]>
  • Loading branch information
pavel-georgiev and Pavel Georgiev committed Nov 24, 2021
1 parent 0de1faa commit af194da
Show file tree
Hide file tree
Showing 3 changed files with 3 additions and 3 deletions.
2 changes: 1 addition & 1 deletion README.md
Original file line number Diff line number Diff line change
Expand Up @@ -57,7 +57,7 @@ Opsani Ignite provides analysis and a number of additional recommendations to im

Best practices require correctly setting resource requirements in a way that meets the performance and reliability requirements of an application (typically, latency and error rate service level objectives), while using assigned resources efficiently to control cloud costs. These values can be discovered manually, often through an onerous and repetitive manual tuning process.

They can also be automatically identified using automatic optimization services, such as the Opsani optimization-as-a-service tool. Those who are interested in how continuous optimization can remediate these issues can go to the [Opsani website](https://opsani.com), set up a [free trial account](https://opsani.com/create-your-account2/#ignite-readme) and attach the optimizer to their application. Connecting an application to the optimizer typically takes 10-15 minutes and, in a few hours, produces concrete, tested resource specifications that can be applied using a simple `kubectl` command.
They can also be automatically identified using automatic optimization services, such as the Opsani optimization-as-a-service tool. Those who are interested in how continuous optimization can remediate these issues can go to the [Opsani website](https://opsani.com), set up a [free trial account](https://console.opsani.com/signup) and attach the optimizer to their application. Connecting an application to the optimizer typically takes 10-15 minutes and, in a few hours, produces concrete, tested resource specifications that can be applied using a simple `kubectl` command.

# Interactive... Stdout... or YAML output

Expand Down
2 changes: 1 addition & 1 deletion cmd/ignite.go
Original file line number Diff line number Diff line change
Expand Up @@ -174,5 +174,5 @@ func runIgnite(cmd *cobra.Command, args []string) {
// display results
displayResults(apps, deployment != "")

fmt.Fprint(os.Stderr, "To optimize your application, sign up for a free trial account at https://opsani.com/create-your-account2/#ignite\n")
fmt.Fprint(os.Stderr, "To optimize your application, sign up for a free trial account at https://console.opsani.com/signup\n")
}
2 changes: 1 addition & 1 deletion cmd/interactive.go
Original file line number Diff line number Diff line change
Expand Up @@ -146,7 +146,7 @@ func (table *AppTable) outputInteractiveRun() {

// create frame
f := tview.NewFrame(t)
f.AddText("To optimize your application, sign up for a free trial account at https://opsani.com/create-your-account2/#ignite", false /*header*/, tview.AlignCenter, 0 /*color*/)
f.AddText("To optimize your application, sign up for a free trial account at https://console.opsani.com/signup", false /*header*/, tview.AlignCenter, 0 /*color*/)
f.SetBorders(0 /*top*/, 0 /*bottom*/, 0 /*header*/, 1 /*footer*/, 0 /*left*/, 0 /*right*/)

// create pages and run
Expand Down

0 comments on commit af194da

Please sign in to comment.