Commit message (Collapse) | Author | Age | Files | Lines | |
---|---|---|---|---|---|
* | Model cloud features explicitly | Martin Polden | 2020-05-06 | 1 | -3/+5 |
| | |||||
* | LogLevel.ERROR -> Level.SEVERE | gjoranv | 2020-04-25 | 1 | -1/+1 |
| | |||||
* | LogLevel.WARNING -> Level.WARNING | gjoranv | 2020-04-25 | 4 | -4/+4 |
| | |||||
* | LogLevel.INFO -> Level.INFO | gjoranv | 2020-04-25 | 1 | -2/+2 |
| | |||||
* | LogLevel.DEBUG -> Level.FINE | gjoranv | 2020-04-25 | 2 | -4/+4 |
| | |||||
* | Import java.util.logging.Level instead of com.yahoo.log.LogLevel | gjoranv | 2020-04-25 | 6 | -6/+6 |
| | |||||
* | Move group argument inside Capacity | Jon Bratseth | 2020-03-25 | 2 | -0/+3 |
| | |||||
* | Reduce logging in service-monitor and orchestrator | Håkon Hallingstad | 2020-03-23 | 1 | -3/+3 |
| | |||||
* | Use two builder methods, request() and specification() | Harald Musum | 2020-03-17 | 1 | -2/+1 |
| | | | | | | | | request() should be used when requesting a cluster, same as old static method called request(). specification() should be used when creating a clsuter spec for an existing cluster, same as old static method from(). specification() will throw an exception if some required fields are not set | ||||
* | Add builder for ClusterSpec | Harald Musum | 2020-03-17 | 1 | -1/+1 |
| | |||||
* | Go back to using cluster spec without docker image repo for infra apps | Harald Musum | 2020-03-16 | 2 | -3/+3 |
| | |||||
* | Use docker image repo in ClusterSpec | Harald Musum | 2020-03-16 | 2 | -3/+5 |
| | |||||
* | Merge pull request #12500 from ↵ | Valerij Fredriksen | 2020-03-09 | 3 | -51/+71 |
|\ | | | | | | | | | vespa-engine/hakonhall/avoid-building-lots-of-applicationinstances Avoid building lots of ApplicationInstances | ||||
| * | Delegate to potentially overloaded method | Håkon Hallingstad | 2020-03-08 | 1 | -1/+1 |
| | | |||||
| * | Avoid building lots of ApplicationInstances | Håkon Hallingstad | 2020-03-08 | 3 | -51/+71 |
| | | | | | | | | | | | | Avoid building a full ApplicationInstance for each node... - for all nodes in the node repo when reporting metrics repo every minute, and - for all nodes in any /nodes/v1/node response | ||||
* | | Also remove hostnames from hostnamesById when removing hosts via application ↵ | Håkon Hallingstad | 2020-03-08 | 2 | -20/+75 |
|/ | | | | | | | | activate I have seen a few "Host not found" messages in CD the last 2 days, and found this bug in how the duper model indices are maintained on application activation. | ||||
* | Throw if accessing duper model while holding status service application lock | Håkon Hallingstad | 2020-03-07 | 5 | -31/+176 |
| | | | | | | | | | | | | When the duper model is updated, ZooKeeper is atomically updated to e.g. remove extraneous hosts. This is done by acquiring the duper model lock first, then the relevant application lock in the status service. Acquiring these two locks in the reverse order may lead to a deadlock. This PR throws an IllegalStateException when detecting the current thread is about to acquire the duper model lock when the current thread has acquired the application lock. | ||||
* | Remove service model cache | Håkon Hallingstad | 2020-03-06 | 5 | -279/+59 |
| | |||||
* | Provide more insight to duper model completeness | Håkon Hallingstad | 2020-03-06 | 2 | -1/+7 |
| | |||||
* | Listening to host changes to the service model | Håkon Hallingstad | 2020-03-04 | 12 | -34/+323 |
| | |||||
* | Merge pull request #12398 from vespa-engine/mpolden/combined-id | Jon Marius Venstad | 2020-03-03 | 1 | -1/+2 |
|\ | | | | | Always use container cluster ID as cluster ID for load balancers | ||||
| * | Add combined ID to ClusterSpec | Martin Polden | 2020-03-02 | 1 | -1/+2 |
| | | |||||
* | | Get previous hostname set | Håkon Hallingstad | 2020-03-01 | 1 | -1/+1 |
| | | |||||
* | | More effective duper model update on activation | Håkon Hallingstad | 2020-03-01 | 1 | -16/+32 |
| | | |||||
* | | Update ↵ | Håkon Hallingstad | 2020-02-29 | 1 | -1/+1 |
| | | | | | | | | | | service-monitor/src/main/java/com/yahoo/vespa/service/model/ApplicationInstanceGenerator.java Co-Authored-By: Valerij Fredriksen <freva@users.noreply.github.com> | ||||
* | | Log and forward duper model completion | Håkon Hallingstad | 2020-02-29 | 7 | -57/+62 |
| | | |||||
* | | Only build part of application instance for host resource | Håkon Hallingstad | 2020-02-28 | 4 | -33/+12 |
| | | |||||
* | | Add host indices to duper model | Håkon Hallingstad | 2020-02-28 | 5 | -50/+157 |
| | | |||||
* | | Moved to more specific methods on ServiceMonitor | Håkon Hallingstad | 2020-02-28 | 11 | -79/+308 |
|/ | |||||
* | Disable service monitor cache | Håkon Hallingstad | 2020-02-25 | 3 | -10/+14 |
| | |||||
* | Fail cfg bootstrap if activation of infra apps fails | Håkon Hallingstad | 2020-02-23 | 1 | -4/+8 |
| | |||||
* | Define completeness of SuperModel and DuperModel | Håkon Hallingstad | 2020-02-23 | 11 | -11/+75 |
| | | | | | | | | | | | | | In order for Orchestrator to remove application data from ZooKeeper, it must know which applications do NOT exist. Since the duper model starts with 0 applications, always, the only way of knowing what applications do not exist is for the bootstrap code to notify the super model/duper model when bootstrap is complete. There are 2 sources of applications that must signal completeness: - The super model, once all applications have been redeployed in ConfigServerBootstrap. - The infrastructure application, in the InfrastructureProvisioner the first time it runs. | ||||
* | Allow dev hosts with only ipv4 | Morten Tokle | 2019-11-15 | 2 | -5/+5 |
| | |||||
* | Support infrastructure applications on devhosts | Morten Tokle | 2019-11-15 | 2 | -3/+24 |
| | |||||
* | Use mockito-core 3.1.0 | Håkon Hallingstad | 2019-10-18 | 8 | -8/+8 |
| | |||||
* | Set user agent | Bjørn Christian Seime | 2019-09-03 | 1 | -0/+1 |
| | |||||
* | Remove unused rotations parameter | Martin Polden | 2019-06-26 | 1 | -1/+1 |
| | |||||
* | Remove ZoneApplication | Valerij Fredriksen | 2019-06-07 | 3 | -202/+5 |
| | |||||
* | Simplify ApplicationInstanceGenerator | Valerij Fredriksen | 2019-06-07 | 2 | -92/+2 |
| | |||||
* | Simplify health monitoring | Valerij Fredriksen | 2019-06-07 | 4 | -118/+3 |
| | |||||
* | Remove enable-tenant-host-app flag | Valerij Fredriksen | 2019-06-07 | 1 | -18/+2 |
| | |||||
* | Make tenant host application supported in DuperModel with feature flag | Valerij Fredriksen | 2019-06-03 | 2 | -5/+30 |
| | |||||
* | Only deploy supported infrastructure applications | Valerij Fredriksen | 2019-06-01 | 2 | -0/+10 |
| | |||||
* | Only allow activate/remove legal infra applications in duper model | Valerij Fredriksen | 2019-06-01 | 2 | -102/+54 |
| | |||||
* | Remove MONITOR_TENANT_HOST_HEALTH flag | Valerij Fredriksen | 2019-06-01 | 5 | -90/+24 |
| | |||||
* | Remove nodeAdminInContainer from configserver.def | Valerij Fredriksen | 2019-06-01 | 1 | -3/+1 |
| | |||||
* | Add logserver container to slobrok monitor manager | Harald Musum | 2019-05-29 | 1 | -9/+6 |
| | |||||
* | Tenant hosts only have node-admin service | Håkon Hallingstad | 2019-05-23 | 2 | -0/+85 |
| | | | | | | | | | | | | Tenant hosts are allocated to the zone (routing) app in the node-admin cluster. These hosts also have various other services like logd, config-sentinel, etc that do not run. The metricsproxy container is a new service that will be added to all hosts, and that will be Slobrok monitored. Except, it will not run on tenant hosts as above. To avoid having metrics cluster spanning the whole of the zone app, and have them DOWN on all tenant hosts, we'll filter those service away from the model when generating the ApplicationInstance of the service model. | ||||
* | Change interface from Mirror.Entry[] to List<Mirror.Entry> as you already ↵ | Henning Baldersheim | 2019-04-22 | 1 | -2/+2 |
| | | | | | | have a list. Avoid having to do an array copy that is not necessary. | ||||
* | Remove unused parameter | Bjørn Christian Seime | 2019-04-08 | 1 | -2/+2 |
| |