tahoe-lafs/trac-2024-07-25
2
0
Issues 1.1k Wiki Activity

Give good DNS name and port number to the public web interface to the test grid. #196

New issue
Closed
opened 2007-10-29 18:22:13 +00:00 by zooko · 7 comments
zooko commented 2007-10-29 18:22:13 +00:00
Owner
Copy link

Somebody asked, mirthfully, what did the "bs" stand for in "tahoebs1.allmydata.com".

Could we add a DNS name such as "testgrid.allmydata.com"? And could we change the port number from 8011 to 8123.

Thanks!

Somebody asked, mirthfully, what did the "bs" stand for in "tahoebs1.allmydata.com". Could we add a DNS name such as "testgrid.allmydata.com"? And could we change the port number from 8011 to 8123. Thanks!
tahoe-lafs added the
operational
minor
enhancement
0.6.1
 labels 2007-10-29 18:22:13 +00:00
warner commented 2007-10-29 22:38:49 +00:00
Author
Owner
Copy link

just FYI, I didn't really intend that to be a public web interface.. it's more for us to develop with. My expectation was that tahoe hackers would be running their own nodes and thus using their own web servers.

The web server on tahoebs1 may disappear at any time.

just FYI, I didn't really intend that to be a public web interface.. it's more for us to develop with. My expectation was that tahoe hackers would be running their own nodes and thus using their own web servers. The web server on tahoebs1 may disappear at any time.
zooko commented 2007-10-30 03:34:16 +00:00
Author
Owner
Copy link

I know you didn't intend that, but it turns out to be really useful for demoing. You can tell people to go to that public web interface and watch a streaming movie, for example. This might be especially interesting to people who do web hosting as a business.

I know you didn't intend that, but it turns out to be really useful for demoing. You can tell people to go to that public web interface and watch a streaming movie, for example. This might be especially interesting to people who do web hosting as a business.
zooko commented 2007-11-01 18:07:56 +00:00
Author
Owner
Copy link

We're focussing on an imminent v0.7.0 (see the roadmap) which hopefully has [#197 #197 -- Small Distributed Mutable Files] and also a fix for [#199 #199 -- bad SHA-256]. So I'm bumping less urgent tickets to v0.7.1.

We're focussing on an imminent v0.7.0 (see [the roadmap](http://allmydata.org/trac/tahoe/roadmap)) which hopefully has [#197 #197 -- Small Distributed Mutable Files] and also a fix for [#199 #199 -- bad SHA-256]. So I'm bumping less urgent tickets to v0.7.1.
zooko commented 2007-11-07 15:51:19 +00:00
Author
Owner
Copy link

As per Norm Hardy's comments on tahoe-dev, we should add documentation and context for people who find http://tahoebs1.allmydata.com:8011. That, or change the URL and don't tell anyone the new one...

As per [Norm Hardy's comments on tahoe-dev](http://allmydata.org/pipermail/tahoe-dev/2007-November/000222.html), we should add documentation and context for people who find <http://tahoebs1.allmydata.com:8011>. That, or change the URL and don't tell anyone the new one...
tahoe-lafs added this to the 0.9.0 (Allmydata 3.0 final) milestone 2008-01-23 02:36:35 +00:00
zandr commented 2008-03-05 00:43:23 +00:00
Author
Owner
Copy link

Err, so what do we want to do here. Hide it, or document it?

Err, so what *do* we want to do here. Hide it, or document it?
secorp commented 2008-03-05 00:53:50 +00:00
Author
Owner
Copy link

Let's document it - I'd like to run a test grid that other people can play with as well. If we need more controlled grids for other testing and/or development, we can make those.

Let's document it - I'd like to run a test grid that other people can play with as well. If we need more controlled grids for other testing and/or development, we can make those.
tahoe-lafs added
0.8.0
 and removed
0.6.1
 labels 2008-03-05 00:53:50 +00:00
zandr commented 2008-03-05 01:14:58 +00:00
Author
Owner
Copy link

http://allmydata.org/trac/tahoe/wiki/TestGrid seems sufficient. Closing.

<http://allmydata.org/trac/tahoe/wiki/TestGrid> seems sufficient. Closing.
tahoe-lafs added the
fixed
 label 2008-03-05 01:14:58 +00:00
zandr closed this issue 2008-03-05 01:14:58 +00:00
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
No results found.
No results found.
Labels
Clear labels   
0.2.0

   
0.3.0

   
0.4.0

   
0.5.0

   
0.5.1

   
0.6.0

   
0.6.1

   
0.7.0

   
0.8.0

   
0.9.0

   
1.0.0

   
1.1.0

   
1.10.0

   
1.10.1

   
1.10.2

   
1.10a2

   
1.11.0

   
1.12.0

   
1.12.1

   
1.13.0

   
1.14.0

   
1.15.0

   
1.15.1

   
1.2.0

   
1.3.0

   
1.4.1

   
1.5.0

   
1.6.0

   
1.6.1

   
1.7.0

   
1.7.1

   
1.7β

   
1.8.0

   
1.8.1

   
1.8.2

   
1.8.3

   
1.8β

   
1.9.0

   
1.9.0-s3branch

   
1.9.0a1

   
1.9.0a2

   
1.9.0b1

   
1.9.1

   
1.9.2

   
1.9.2a1

   
LeastAuthority.com automation

   
blocker

   
cannot reproduce

   
cloud-branch

   
code

catch-all for anything that can be fixed by writing code but isn't classified better

  
code-dirnodes

anything involving tahoe directories

  
code-encoding

immutable-file encoding format/layout, cap format, encoding/decoding algorithms

  
code-frontend

general frontend things: new user-facing interfaces, FTP/SFTP servers, FUSE-like interfaces

  
code-frontend-cli

CLI tools

  
code-frontend-ftp-sftp

   
code-frontend-magic-folder

   
code-frontend-web

webapi interfaces, user-facing "WUI" interfaces

  
code-mutable

anything involving mutable files: encoding/decoding, share format

  
code-network

Introducer, locating storage servers, establishing/maintaining connections to them

  
code-nodeadmin

node startup/shutdown, tools to create nodes, logging tools, management/monitoring tools, manhole, disk-space-limiting tools

  
code-peerselection

server selection/sorting algorithm, rebalancing code, allocation policy, swarming-download

  
code-storage

storage-server implementation, share-storage directory layout, client-to-server share transfer protocol

  
contrib

problems with non-core things that live in the source:contrib/ directory

  
critical

   
defect

   
dev-infrastructure

things that help us build Tahoe: buildbot, automated speed/memory/code-coverage tests and results-displayers, IRC channels, mailing lists, this Trac instance

  
documentation

docs items. Also use 'docs' keyword on tickets in more specific components.

  
duplicate

   
enhancement

   
fixed

   
invalid

   
major

   
minor

   
n/a

   
normal

   
operational

things involved in running a tahoe grid, external tools to monitor/maintain a grid (like "nodeadmin" but larger-scale). Was also used for issues with the allmydata.com grid.

  
packaging

setup.py script, library dependencies, binary packages, licensing, installation instructions

  
somebody else's problem

   
supercritical

   
task

   
trivial

   
unknown

Uncategorized. All tickets default to this component until someone updates it.

  
was already fixed

   
website

things about the tahoe-lafs.org website (and sometimes this Trac instance, shared with 'dev-infrastructure')

  
wontfix

   
worksforme
No labels
0.2.0
0.3.0
0.4.0
0.5.0
0.5.1
0.6.0
0.6.1
0.7.0
0.8.0
0.9.0
1.0.0
1.1.0
1.10.0
1.10.1
1.10.2
1.10a2
1.11.0
1.12.0
1.12.1
1.13.0
1.14.0
1.15.0
1.15.1
1.2.0
1.3.0
1.4.1
1.5.0
1.6.0
1.6.1
1.7.0
1.7.1
1.7β
1.8.0
1.8.1
1.8.2
1.8.3
1.8β
1.9.0
1.9.0-s3branch
1.9.0a1
1.9.0a2
1.9.0b1
1.9.1
1.9.2
1.9.2a1
LeastAuthority.com automation
blocker
cannot reproduce
cloud-branch
code
code-dirnodes
code-encoding
code-frontend
code-frontend-cli
code-frontend-ftp-sftp
code-frontend-magic-folder
code-frontend-web
code-mutable
code-network
code-nodeadmin
code-peerselection
code-storage
contrib
critical
defect
dev-infrastructure
documentation
duplicate
enhancement
fixed
invalid
major
minor
n/a
normal
operational
packaging
somebody else's problem
supercritical
task
trivial
unknown
was already fixed
website
wontfix
worksforme
Milestone
Clear milestone
No items
No milestone
0.9.0 (Allmydata 3.0 final)
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: tahoe-lafs/trac-2024-07-25#196
No description provided.
Delete branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?