Releases: HubSpot/Baragon
Releases · HubSpot/Baragon
Baragon-0.2.0
Check out the 0.2.0 Milestone to see all bug fixes and features in detail.
Upgrading
It is recommended to upgrade BaragonService
before BaragonAgentService
for this release. However, the new multiple domains feature will not function correctly until both components are updated.
New Features
- #162 - Support locking additional paths for a single service
- #165 - Support for regex-based paths
- #167 - Support for multiple domains in a single group (extra variables in template path, render multiple per template)
Other Changes and Bug Fixes
- #164 - Upgrade basepom
- #163 - Better base path conflict message
- #161 - Ensure a duplicate upstream with no rack is not deleted
- #160 - Lock brunch to 2.2.x
- #157 / #158 - Additional handlebars helpers for dealing with racks/weighting
- #156 - UI improvements and bump to brunch 2
- #154 - Upgrade Horizon version
- #152 - Only render templates if they are not empty
- #151 - Handle a null Stat from zk
- #150 - Don't require base path lock for a service delete with no upstreams
Deprecations
- In
LoadBalancerConfiguration
(Baragon Agent configuration field), thedomain
field is now deprecated. Due to the fact that a single agent can now support multiple domains, thedomain
field in theloadBalancerConfig
section has been replaced withdefaultDomain
(String) anddomains
(List) fields. Eitherdomain
ordefaultDomain
may be specified, howeverdefaultDomain
will take precedence anddomain
will be removed in the next release. This change is also reflected in theBaragonGroup
object. - In
BaragonAgentMetadata
thedomain
field will be removed in the next release. Domain information will instead only be available in theBaragonGroup
object which is updated by the agent at startup time
Thanks
Baragon-0.1.12
Check out the 0.1.12 Milestone to see all bug fixes and features in detail.
Changes
- Make less api calls to the aws ELB api while syncing load balancer instances
- Build curator without NamespaceFacade
- Default Sentry configuration to absent
- Fix a bug in underscore version resolution for the UI build
Thanks
Baragon-0.1.11
Check out the 0.1.11 Milestone to see all bug fixes and features in detail.
Announcements
- Due to changes in the way upstreams are stored in zookeeper, for this release it is recommended that you first upgrade all
BaragonAgentService
instances before upgradingBaragonService
- All writes to the global state zookeeper node
/state
will be removed in the next release. Global state will still be available via the /state api endpoint, but will be calculated and cached in BaragonService rather than writing the data to a zk node
Important Changes
- #121 - Global state can now be recomputed asynchronously
- #124 - Baragon agents will now get global state for bootstrapping from the BaragonService api instead of zk
- #130 - Service and upstream data will now commit as part of a single zk transaction. Upstream data is also stored as part of the zk path name. A zk migration on startup will automatically convert your data to the new format
- #137 - BaragonService now supports sentry integration
- #140 - ElbSync will now check that vpc id matches before trying to add to an elb
- #144 - BAragonAgentMetadata is now available for use in agent templates
Thanks
Baragon-0.1.10
Important
- bugfix from version 0.1.9 for use of the Reentrant lock when re-applying configs after reconnecting to zookeeper.
Baragon 0.1.9
_BUG_
It was found that this release contains a bug where a lock is not released properly when agents reapply configs after reconnection to zookeeper. Please use 0.1.10 instead.
Check out the 0.1.9 milestone to see new features / bugfixes in detail.
Announcements
- This release contains changes to how request data is stored in zookeeper. When started baragon will convert all data for hstorical requests from the old format to the new. Be aware this may take a few minutes. See #96 for details about the associated changes
Important
- #110 -- optionally update state node on a schedule, in the background
- #109 -- add metrics for zk calls and lb adapter calls
- #106 -- Optionally enforce target number of agents
- #105 -- save failed configs for later inspection
- #103 -- check config validity on an interval and cache the result
- #102 -- noVerify/noReload options
- #101 -- Max number of requests to keep/return to ui per service
- #100 -- Stay in sync after losing connection
- #97 -- Ui + Auth
- #96 -- Purge Old Requests
- #88 -- State file
- #87 -- add optional extraAgentData to BaragonAgentMetadata
- #86 -- add ok-to-shutdown endpoint to BaragonService
- #85 -- configurably retry startup/shutdown calls to service
- #83 -- non-existent response should be RETRY not WAITING status
Thanks
Baragon-0.1.8
- Add replaceUpstreams functionality as an alternative to using addUpstreams/removeUpstreams
- Move to HubSpot basepom
- Fixes to ELB Syncing
- keep track of agent availability zone
- enable availability zones before adding to ELB
- add correctly for both vpc and classic ELBs
- Use Ec2MetadataUtils to gather agent info
- refactor add/don't add logic
- Add configurable agent registration with service on startup and graceful shutdown
Baragon-0.1.7
- move to basepom
- Refactor agents to accept remove, reload, and update request actions
- Add capability to sync active agents with an ELB
- Faster agent bootstrap
Baragon-0.1.6
- BaragonUI
- Support for multiple templates
- Customizable jar names
Baragon 0.1.5
- vagrant box
- more docs
- BaragonClient
- track known agents
- properly handle exceptions thrown in
commitRequest()
- allow arbitrary upstream values (not just
hostname:port
) - fixes to base path locks (i.e. clear lock if all upstreams removed)
- unittests!!!
- refactoring of internal state machine
- Chef cookbook (thanks @eherot @jeffbyrnes)
- add read-only mode (
BaragonRequestWorker
disabled) - support service renames
- handles ZK issues more robustly thanks to fixes in response to chaos monkey testing
- add
BaragonWatcher
, allowing other services to subscribe to Baragon updates
Baragon-0.1.0
- @tpetr: everything.